• 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.

Issue Suspended Websites display Internal Server Error 500 instead of 503

JonScheel

New Pleskian
I'm new to Plesk, having purchased a Windows VPS server through GoDaddy. This could be a simple fix and I'm just not seeing it due to my inexperience.

When a website is placed in "suspend" mode, the server throws up the 500 error instead of saying the site is down for maintenance (error 503). The logs are very unhelpful, merely saying that it tried to get a page and that it returned 500... and also tried to get a favicon.ico which also returned 500.

Here's what my IIS log has for each failed attempt...

#Fields: date time s-sitename s-computername s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs-version cs(User-Agent) cs(Cookie) cs(Referer) cs-host sc-status sc-substatus sc-win32-status sc-bytes cs-bytes time-taken
2017-07-13 21:29:59 W3SVC18 SRVR0 <serverIPaddress> GET / - 80 - <clientIP> HTTP/1.1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/59.0.3071.115+Safari/537.36 PHPSESSID=veq8m29ukbv3v4vf6olfs223q1 - <domainname> 500 50 33 1657 467 124
2017-07-13 21:29:59 W3SVC18 SRVR0 <serverIPaddress> GET /favicon.ico - 80 - <clientIP> HTTP/1.1 Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/59.0.3071.115+Safari/537.36 PHPSESSID=veq8m29ukbv3v4vf6olfs223q1 <domainname> 500 50 33 1657 464 31

So if I'm reading them right, 500.50 (sub status) is a rewrite error occurred in RQ_BEGIN_REQUEST notification handling. But I have no clue where to go to fix that or why it would be occurring.

Any help would be appreciated. Thanks in advance.
 
I can't reproduce your problem on the test servers (getting 503 error in case of Plesk 12.0, 12.5, 17.5). Could you tell me please which version of Plesk do you use?
 
I'm on Plesk Onyx 17.0.17 Update #29, last updated on July 10, 2017 12:55 AM (according to the control panel) :)
 
Also, in doing some more digging on this, I checked the URL Rewrite rules within IIS itself, just in case that was part of the issue. I did have some custom rules in there, so I deleted them... but that had no effect on this error. It still goes to 500.50 when trying to browse to that website whether there are any <rewrite> rules in the web.config or not.

However, when a site has been set to "suspend", then the URL Rewrite area of IIS 7.5 throws an error when trying to open it to view the rules.
fcqi34.jpg

Not sure if that's important or not.
 
I didn't reproduced the problem on Plesk 17.0 either. Please try to create another domain (or subdomain) and check the behaviour. Maybe customized rewrite rules or some other settings has an influence.
 
I have the identical issue with 30+ domains on the server. The instant I try to suspend any of them, I run into the 500 error. :(
I'm going to be getting a new server from GoDaddy soon, so I'll try it with a default configuration and see what happens and report back.
 
Back
Top