Facebook
Twitter-
Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
To continue sharing your ideas and feedback, please visit features.plesk.com
abdi
Platinum Pleskian
Hello Koman,
500 Error is a PHP Error. It means there is a problem with any of your php files or application.
For security reasons, you will not see the actual PHP error on your pages except through your log files ...
Instead, you can always find the exact reported errors by navigating to your error logs ..
The error could be as a result of a broken database connection link, you might need to verify and check that ALL your DB settings are correct.
*If you need my help to check it out for you, just ask
500 Error is a PHP Error. It means there is a problem with any of your php files or application.
For security reasons, you will not see the actual PHP error on your pages except through your log files ...
Instead, you can always find the exact reported errors by navigating to your error logs ..
The error could be as a result of a broken database connection link, you might need to verify and check that ALL your DB settings are correct.
*If you need my help to check it out for you, just ask
There's actually many reasons why you could get a server 500 error and not just PHP related (although it could be part of it. For an example, a plugin that was solely designed to work with Linux and never took the Windows environment into consideration, although miner you can normally modify the code to work).
To troubleshoot this correctly I would recommend that you check out the following articles that talks about enabling tracing and troubleshooting server error codes.
http://www.iis.net/learn/troublesho...cing/troubleshoot-with-failed-request-tracing
http://www.iis.net/learn/troublesho...shooting-failed-requests-using-tracing-in-iis
The more we know about the actual error by looking at the trace logs and what not the better chances we can pinpoint the fix.
To troubleshoot this correctly I would recommend that you check out the following articles that talks about enabling tracing and troubleshooting server error codes.
http://www.iis.net/learn/troublesho...cing/troubleshoot-with-failed-request-tracing
http://www.iis.net/learn/troublesho...shooting-failed-requests-using-tracing-in-iis
The more we know about the actual error by looking at the trace logs and what not the better chances we can pinpoint the fix.
Similar threads
