Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1] 2
1
Nginx / NGINX Configuration for Load Balancer
« on: June 26, 2023, 09:18:48 PM »
NGINX Configuration for Load Balancer
At the moment is shows the default HTML page, I think I need to modify the configuration but not sure what and where?
Just a single load balance to a single server at this stage.
Any helps, tips, recommendations would be great. It is fairly new to me.
At the moment is shows the default HTML page, I think I need to modify the configuration but not sure what and where?
Just a single load balance to a single server at this stage.
Any helps, tips, recommendations would be great. It is fairly new to me.
2
Nginx / upstream timed out (110: Connection timed out) - Getting it frequently
« on: May 09, 2023, 02:10:22 AM »
Hi all,
I am getting the following errors every now and then on my WordPress site.
Any tips or recommendations?
I am getting the following errors every now and then on my WordPress site.
Code: [Select]
2023/05/09 12:00:45 [error] 9507#9507: *628 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 103.154.154.179, server: whocalled.au, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au", referrer: "https://whocalled.au/wp-admin/post.php?post=85931400&action=edit"
2023/05/09 12:01:05 [error] 9506#9506: *633 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 207.136.12.25, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au", referrer: "https://www.google.com.au/"
2023/05/09 12:02:45 [error] 9507#9507: *649 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 103.154.154.179, server: whocalled.au, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au", referrer: "https://whocalled.au/wp-admin/post.php?post=1162424&action=edit"
2023/05/09 12:03:45 [error] 9505#9505: *655 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 103.154.154.179, server: whocalled.au, request: "POST /wp-admin/admin-ajax.php HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au", referrer: "https://whocalled.au/wp-admin/post.php?post=85931400&action=edit"
2023/05/09 12:05:04 [error] 9505#9505: *655 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 103.154.154.179, server: whocalled.au, request: "GET /landline/0735207691/ HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au", referrer: "https://whocalled.au/landline/0735207691/"
2023/05/09 12:05:51 [error] 9507#9507: *686 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 110.142.158.81, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au", referrer: "https://www.google.com/"
2023/05/09 12:05:55 [error] 9508#9508: *688 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 45.64.58.134, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au", referrer: "https://www.google.com/"
2023/05/09 12:05:57 [error] 9508#9508: *688 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 2001:8003:d803:f000:c880:7b5c:48e3:ae3e, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au", referrer: "https://www.google.com.au/"
2023/05/09 12:05:58 [error] 9507#9507: *686 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 35.225.82.182, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au"
2023/05/09 12:06:10 [error] 9508#9508: *688 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 172.105.190.118, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au"
2023/05/09 12:06:13 [error] 9480#9480: *693 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 120.17.148.100, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au", referrer: "https://www.google.com.au/"
2023/05/09 12:06:17 [error] 9508#9508: *688 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 103.154.154.179, server: whocalled.au, request: "GET /business-listings/score-debt-collection/ HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au", referrer: "https://scoredebtcollection.com.au/"
2023/05/09 12:06:18 [error] 9505#9505: *696 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 202.153.219.106, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au", referrer: "https://www.google.com/"
2023/05/09 12:06:23 [error] 9505#9505: *655 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 66.249.70.200, server: whocalled.au, request: "GET /mobile/0400005696/ HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au"
2023/05/09 12:06:43 [error] 9505#9505: *696 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 143.42.97.213, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au"
2023/05/09 12:06:45 [error] 9505#9505: *696 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 172.104.109.161, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au"
2023/05/09 12:06:45 [error] 9505#9505: *696 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 45.33.100.21, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au"
2023/05/09 12:06:47 [error] 9481#9481: *682 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 1.200.58.189, server: whocalled.au, request: "GET /mobile/0406907272/ HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au"
2023/05/09 12:06:47 [error] 9507#9507: *684 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 2001:8004:4532:b9f4:a148:4edb:cf85:4b0f, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock", host: "whocalled.au", referrer: "https://www.google.com/"
2023/05/09 12:06:50 [error] 9480#9480: *693 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock failed (11: Resource temporarily unavailable) while connecting to upstream, client: 172.105.169.250, server: whocalled.au, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/nobody.sock:", host: "whocalled.au"Any tips or recommendations?
3
Nginx / Re: All my site are now showing 502 Bad Gateway nginx/1.20.2
« on: April 11, 2023, 02:17:28 AM »When compiling new php-fpm versions, you don't automatically get a user.conf file created (and therefore a user.sock file). You should copy over your existing user.conf from the previous PHP version, change the paths therein appropriately for that PHP version, and restart that version of php-fpm.
But I don't have an existing sock file to copy from unless I missing something? Where should I be looking for an existing one?
restart that version of php-fpm.
How do you do this? I've tried multiple commands and Google's with 0 success.
Also, I see you are using php 8.0. Any specific reason you are not using 8.1 instead? If not, I would recommend compiling 8.1 and using that instead of 8.0.
Just what I have started off with and some of my WordPress plugins are not compatible with 8.1 yet.
4
Nginx / Re: All my site are now showing 502 Bad Gateway nginx/1.20.2
« on: April 10, 2023, 10:24:13 PM »
I do have had this problem and believe it is related to the .sock file missing for the user.
I rectified it temporarily by modifying my website .conf file to change the socket file to nobody.sock but it just means I lose some functionality in the backend of the Wordpress site, like not being able to install plugins directly and getting some permissions errors.
This is NOT a permanent fix. I would love to have a better solution.
Code: [Select]
2023/04/11 06:59:29 [crit] 5018#5018: *113 connect() to unix:/opt/alt/php-fpm80/usr/var/sockets/whocalau.sock failed (13: Permission denied) while connecting to upstream, client: 103.154.154.179, server: whocalled.au, request: "GET /wp-admin/plugin-install.php?s=w3%2520total&tab=search&type=term HTTP/1.1", upstream: "fastcgi://unix:/opt/alt/php-fpm80/usr/var/sockets/whocalau.sock:", host: "whocalled.au", referrer: "https://whocalled.au/wp-admin/plugins.php"
I rectified it temporarily by modifying my website .conf file to change the socket file to nobody.sock but it just means I lose some functionality in the backend of the Wordpress site, like not being able to install plugins directly and getting some permissions errors.
This is NOT a permanent fix. I would love to have a better solution.
5
Apache / proxy_fcgi:error | The timeout specified has expired | AH01075 Error dispatching
« on: February 22, 2023, 07:17:55 PM »
Hi all,
I've tried googling this and had 0 luck with anything.
Here are the error logs:
Cannot resolve the timeout issues (504 errors).
I've tried changing the apache timeout. It only affects the front end of the website, not the back end (unless I am searching for something).
I've got this happening on two sites, two fresh CWP installs on new fresh Linode instances.
I am running Apache with PHP 8.0.x as the FPM set version. The memory limit, execution timeout etc are all very high, so I don't believe its that.
I've looked at https://stackoverflow.com/questions/33375823/apache-proxfy-fcgi-error-dispatching-request-to but anything like changing the http.conf file and the timeout just breaks apache!
Any help would be great.
I've tried googling this and had 0 luck with anything.
Here are the error logs:
Code: [Select]
[Wed Feb 22 19:04:10.797226 2023] [proxy_fcgi:error] [pid 5226:tid 140195114481408] (70007)The timeout specified has expired: [client 162.158.2.142:41656] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:05:05.075830 2023] [proxy_fcgi:error] [pid 5226:tid 140195122874112] (70007)The timeout specified has expired: [client 162.158.2.143:17306] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:05:20.549705 2023] [proxy_fcgi:error] [pid 5227:tid 140195089303296] (70007)The timeout specified has expired: [client 172.69.62.16:46224] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/admin-ajax.php?action=ai1wm_export&ai1wm_import=1
[Wed Feb 22 19:05:26.516750 2023] [proxy_fcgi:error] [pid 5227:tid 140195156444928] (70007)The timeout specified has expired: [client 162.158.2.142:16522] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:07:56.570682 2023] [proxy_fcgi:error] [pid 5227:tid 140195122874112] (70007)The timeout specified has expired: [client 162.158.2.194:63062] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:07:58.850561 2023] [proxy_fcgi:error] [pid 5226:tid 140195131266816] (70007)The timeout specified has expired: [client 162.158.2.194:63068] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:07:59.297431 2023] [proxy_fcgi:error] [pid 5226:tid 140195282851584] (70007)The timeout specified has expired: [client 162.158.2.195:51274] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:08:01.532698 2023] [proxy_fcgi:error] [pid 5227:tid 140195114481408] (70007)The timeout specified has expired: [client 172.70.38.137:37218] AH01075: Error dispatching request to : (polling)
[Wed Feb 22 19:08:20.023717 2023] [proxy_fcgi:error] [pid 5227:tid 140195181623040] (70007)The timeout specified has expired: [client 172.68.146.37:14536] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/admin-ajax.php?action=ai1wm_export&ai1wm_import=1
[Wed Feb 22 19:08:31.217193 2023] [proxy_fcgi:error] [pid 5227:tid 140195064125184] (70007)The timeout specified has expired: [client 172.68.210.37:40268] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-cron.php?doing_wp_cron=1677092851.1226348876953125000000
[Wed Feb 22 19:08:44.524789 2023] [proxy_fcgi:error] [pid 5226:tid 140195181623040] (70007)The timeout specified has expired: [client 162.158.2.195:34562] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=landline
[Wed Feb 22 19:08:54.516715 2023] [proxy_fcgi:error] [pid 5226:tid 140195089303296] (70007)The timeout specified has expired: [client 162.158.2.195:15688] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=business_listings
[Wed Feb 22 19:08:55.327695 2023] [proxy_fcgi:error] [pid 5227:tid 140195089303296] (70007)The timeout specified has expired: [client 162.158.2.194:57594] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:08:55.710860 2023] [proxy_fcgi:error] [pid 5226:tid 140195072517888] (70007)The timeout specified has expired: [client 162.158.2.194:57606] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:09:17.338724 2023] [proxy_fcgi:error] [pid 5227:tid 140195266066176] (70007)The timeout specified has expired: [client 162.158.2.194:40668] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:10:55.478676 2023] [proxy_fcgi:error] [pid 5227:tid 140195055732480] (70007)The timeout specified has expired: [client 162.158.2.142:14980] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=business_listings
[Wed Feb 22 19:10:55.529674 2023] [proxy_fcgi:error] [pid 5227:tid 140195047339776] (70007)The timeout specified has expired: [client 162.158.2.143:43260] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:10:56.517813 2023] [proxy_fcgi:error] [pid 5330:tid 140195106088704] (70007)The timeout specified has expired: [client 162.158.2.143:56790] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=mobile
[Wed Feb 22 19:11:00.506680 2023] [proxy_fcgi:error] [pid 5227:tid 140195072517888] (70007)The timeout specified has expired: [client 162.158.2.142:47564] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-admin/edit.php?post_type=landline
[Wed Feb 22 19:11:38.359023 2023] [proxy_fcgi:error] [pid 5227:tid 140195080910592] (70007)The timeout specified has expired: [client 172.68.146.58:15386] AH01075: Error dispatching request to : (polling), referer: https://whocalled.au/wp-cron.php?doing_wp_cron=1677093038.0755450725555419921875Cannot resolve the timeout issues (504 errors).
I've tried changing the apache timeout. It only affects the front end of the website, not the back end (unless I am searching for something).
I've got this happening on two sites, two fresh CWP installs on new fresh Linode instances.
I am running Apache with PHP 8.0.x as the FPM set version. The memory limit, execution timeout etc are all very high, so I don't believe its that.
I've looked at https://stackoverflow.com/questions/33375823/apache-proxfy-fcgi-error-dispatching-request-to but anything like changing the http.conf file and the timeout just breaks apache!
Any help would be great.
6
Apache / Re: Robots being provided a 500 error
« on: December 02, 2021, 06:58:23 PM »Quote
try to check domainlogs error_log...can be mod_security
I don't have mod_security installed.
After some further trial and error, I tried to even upload files and was getting errors. In the end, I terminated that account (since it was the only one with the issue) and started fresh. Issue now resolved.
7
Apache / Re: Robots being provided a 500 error
« on: December 02, 2021, 05:50:37 AM »
http://forum.centos-webpanel.com/apache/apache-not-loading-sites-well-after-cwp-to-cwppro-version-0-9-8-244/ < I did the same thing and I recently did updates which broke it! CWP upgrade broke it.
8
Apache / Re: Robots being provided a 500 error
« on: December 02, 2021, 05:27:20 AM »Code: [Select]
17.121.114.44 - - [02/Dec/2021:16:25:56 +1100] "GET /robots.txt HTTP/1.1" 500 127 "-" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.1 Safari/605.1.15 (Applebot/0.1; +http://www.apple.com/go/applebot)"
9
Apache / Re: Robots being provided a 500 error
« on: December 02, 2021, 05:21:09 AM »Code: [Select]
103.xxx.xxx.xxx - - [02/Dec/2021:16:20:42 +1100] "GET /robots.txt HTTP/1.1" 500 127 "-" "Screaming Frog SEO Spider/16.3"
103..xxx.xxx.xxx - - [02/Dec/2021:16:20:42 +1100] "GET / HTTP/1.1" 500 32997 "-" "Screaming Frog SEO Spider/16.3"
10
Apache / Re: Robots being provided a 500 error
« on: December 02, 2021, 05:19:00 AM »Code: [Select]
172.105.169.250 - - [02/Dec/2021:16:15:01 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.173.108 - - [02/Dec/2021:16:15:21 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.169.250 - - [02/Dec/2021:16:15:58 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.169.250 - - [02/Dec/2021:16:16:23 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.190.118 - - [02/Dec/2021:16:16:57 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.190.118 - - [02/Dec/2021:16:17:25 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.169.250 - - [02/Dec/2021:16:18:02 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
172.105.190.118 - - [02/Dec/2021:16:18:27 +1100] "GET / HTTP/1.1" 500 32997 "-" "Better Uptime Bot Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.169 Safari/537.36"
11
Apache / Robots being provided a 500 error
« on: December 02, 2021, 05:14:47 AM »
For some reason any robots are being provided with a 500 internal server error. But users are okay?
Any ideas? CWP Pro on Centos 7.
Tried updating PHP and server updates with no fix.
Any ideas? CWP Pro on Centos 7.
Tried updating PHP and server updates with no fix.
12
CentOS-WebPanel Bugs / Re: Quota Not Updating
« on: November 30, 2021, 07:14:02 PM »
After further look. Seems like you cannot set Disk Space as "-1" for unlimited. It needs to be an actual number. But you don't get the error when you update an existing package, only when you create a new package which is how I found it.
Updated the space size and its right to go.
Updated the space size and its right to go.
13
CentOS-WebPanel Bugs / Quota Not Updating
« on: November 29, 2021, 10:27:56 PM »
Hi all,
Updated the Packages and the Storage Quota hasn't updated.
Did all server updates and still nothing. Haven't done a reboot.
Running CWP Pro.
Thanks.
Updated the Packages and the Storage Quota hasn't updated.
Did all server updates and still nothing. Haven't done a reboot.
Running CWP Pro.
Thanks.
14
E-Mail / Re: Emails Not Delivering | PHP Mail Not Working | Time Out Errors
« on: June 24, 2021, 10:13:16 PM »
Got Linode to unblock the ports and good to go!
15
E-Mail / Re: Emails Not Delivering | PHP Mail Not Working | Time Out Errors
« on: June 24, 2021, 06:39:14 AM »
http://forum.centos-webpanel.com/index.php?topic=10765.msg37109#msg37109 - This could be the issue since moving Linode.
I have submitted a ticket with them.
I have submitted a ticket with them.
Pages: [1] 2
