• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Only some web requests getting 503 error

varun33

New Pleskian
Issue
Some users are getting a 503 error (around 5-6 users a day) and the error does not go away with a refresh of the page. Once that error pops-up any page requested on the domain throws the same 503 error. There is no specific website or domain from the ones configured on the server where this error is being faced it is just random.

Errors in the log

(Apache)
AH01067: Failed to read FastCGI header
[proxy_fcgi:error] [pid 30805:tid 140427730589440](104)Connection reset by peer: [client xxx.xxx.xxx.xxx:41520] AH01075: Error dispatching request to :
(Syslog)
localhost kernel: [2043980.836123] php-fpm[65943]: segfault at 7fff2417ab40 ip 000056425a0108dc sp 00007fff2417ab20 error 6 in php-fpm[564259d59000+4c4000]

Server Environment

Ubuntu 18.04.1 LTS
CPU: 1 processor with 16 cores
RAM: 48G
Plesk Onyx Version 17.8.11 Update #35
PHP 7.2.13
FPM application served by Apache
SSL enabled on all domains
Nginx Proxy mode enabled along with smart static files processing
Linux+Nginx+Apache2+PHP-FPM-7.2+HTTP2+MySQL (mariadb)
15 domains configured with the above settings all running under a common wordpress multisite installation

Background
We recently migrated to the above server, before this we were using PHP 5.6.33 with FastCGI and did not have any such issues.

Our analysis
- No issues with the availability of CPU/memory as the average load is around 3-4 and there is at least 24G of memory available
- We are unable to replicate the issue and it just happens
- We have found that on the web browser if the issue occurs we can delete the wordpress cookie 'wordpress_logged_in_*******' and that fixes the issue and allows to open the requested page instead of a 503

We are still trying to find the cause for this issue but if any of you have faced this or a similar problem please share your version and the solution if you were able to find it.

Thank you.
 
Last edited:
Well this issue was discussed on the forum many times and there are different approaches for it.
Also, there are several related KB articles where different reasons for this issue were described, you can just try for example to use phrase "AH01075: Error dispatching request to" for KB search.

maybe this one will be a starting point for you
WordPress website shows 503 Service Temporarily Unavailable on Plesk for Linux: AH01075: Error dispatching request to
WordPress website shows 503 Service Temporarily Unavailable
 
Last edited:
Switching to 7.1.26 gives a 503 error and after removing the php extension "ioncube_loader_lin_7.1" it turns into a 502 error.

Switching to 7.3.1 gives a 502 error.
 
Last edited:
We finally managed to resolve the issue. The problem was with the wordpress plugin "iThemes Security", due to a bug in the plugin related to expired wordpress login keys there was an infinite loop being created which ultimately lead to the 502/503 error.

Thank you all for your help.
 
Back
Top