Turkey (Turkish)
Germany (German)
Worldwide (English)
ApplicationPHP fatal error and plugin conflicts
Halkali merkez neighborhood fatih st ozgur apt no 46 , Kucukcekmece , Istanbul , 34303 , TR
HTTP 500 indicates an unexpected error occurred while the application or web server was processing the request. On Plesk, the same 500 screen can occur due to a faulty .htaccess, PHP fatal error, memory limit, FastCGI timeout, file permission, or web configuration.
500 Internal Server Error
Allowed memory size of 134217728 bytes exhausted
mod_fcgid: read data timeout in 45 seconds
Premature end of script headers: index.php
Request exceeded the limit of 10 internal redirectsThe 500 code does not identify a single failure. The server has received the request but was unable to complete the process. Therefore, instead of changing the error screen of the page, the full message and timestamp in the Plesk domain log should be found.
Adding PHP handler unsupported php_value or php_flag lines to .htaccess can stop configuration parsing.
The Allowed memory size exhausted message indicates that the application has consumed the memory_limit value defined for the domain. The extension or process that consumes it should be investigated before increasing the limit.
mod_fcgid read data timeout and Premature end of script headers messages indicate that the FastCGI process ended without responding or exceeded the time limit.
Too many internal redirects can occur due to incorrect HTTP→HTTPS redirection, www redirection, or WordPress rewrite rules creating a loop.
Opening display_errors in production may reveal file paths and sensitive information to visitors. Error details should be obtained from domain logs or a temporary test environment accessible only to the administrator IP.
Search for the phrase you see in the email, browser, or SSH log. Each card includes meaning, probable cause, and safe initial action.
Meaning: An unexpected error occurred while the server was processing the request.
Possible cause: PHP fatal error, web configuration, permission or handler issue.
Meaning: PHP process has consumed the memory_limit value.
Possible cause: Heavy plugin, large data processing, infinite loop, or low limit.
Meaning: Data could not be retrieved from the FastCGI process in time.
Possible cause: Long-running PHP process, SQL delay, or low FcgidIOTimeout.
Meaning: CGI/FastCGI process terminated without producing a valid HTTP header
Possible cause: Fatal error, segfault, permission or wrapper issue.
Meaning: The used handler does not support the .htaccess php_value directive.
Possible cause: The Apache mod_php rule has been confused with PHP-FPM/FastCGI.
Meaning: The request has entered a redirection loop on the server.
Possible cause: Conflicting HTTPS, www, language, or CMS rewrite rules.
Meaning: The web server is unable to read or execute the file.
Possible cause: Incorrect ownership, 000 permissions, parent directory access or SELinux.
Meaning: A PHP code has thrown an uncaught or unhandled exception.
Possible cause: Incompatible PHP version, missing class, corrupted file, or update.
No records matching this expression were found.
Commands are for root access. Collect only status and logs first; Do not change the permanent setting without seeing the reason.
tail -n 200 /var/www/vhosts/system/example.com/logs/error_log
tail -n 100 /var/www/vhosts/system/example.com/logs/proxy_error_logDisplays PHP, Apache, and proxy messages at HTTP 500.
curl -skIL --max-redirs 15 https://example.com/The loop of HTTPS and www rules is shown with Location headers.
cp -a /var/www/vhosts/example.com/httpdocs/.htaccess /root/htaccess-example.com.bak
grep -nE 'php_value|php_flag|RewriteRule|Redirect' /var/www/vhosts/example.com/httpdocs/.htaccessList the risky directives and instructions without deleting the file.
plesk bin domain --info example.com | grep -Ei "PHP|Hosting"
grep -R "memory_limit" /var/www/vhosts/system/example.com/conf/ 2>/dev/null | tailDomain configuration helps to examine related information PHP
namei -l /var/www/vhosts/example.com/httpdocs/index.php
stat /var/www/vhosts/example.com/httpdocs/index.phpDisplays the access permissions of all directories leading to the file.
plesk repair web example.com
plesk repair fs example.comDomain web configuration and Plesk expected file system structure check
php -l /var/www/vhosts/example.com/httpdocs/index.phpChecks the parse error issue in a specific PHP file without running the application.
First locate the error message; then sequentially isolate the .htaccess, PHP, permissions, and web configuration layers.
Note the full URL, time, and process that gives the 500. This information is necessary to find the correct request in the log search.
Focus on the first meaningful fatal, invalid command, or permission message in the chain instead of the last line of the log.
tail -n 200 /var/www/vhosts/system/example.com/logs/error_logBackup the file. Isolate new added PHP or rewrite lines one by one; do not delete the file directly.
If there is a fatal error or a memory error, check the compatibility of the selected PHP version with the extension, theme, and application.
Use Plesk repair command first for interactive control; do not run extensive automatic repair without viewing results.
plesk repair web example.comAfter the page loads, make sure a new fatal line does not appear, and that cron and form-like dynamic operations are working.
curl -skI https://example.com/The error log in wp-content is checked for plugin and theme compatibility. Plugins can be disabled either from the database or from the file name in a controlled manner.
New directives may be incompatible with the handler. Compare backups and separate php_value and rewrite rules.
memory_limit, max_execution_time, upload limits, and the application's support for processing in parts are evaluated.
Plesk redirection, Cloudflare Flexible SSL, and CMS site URL settings are checked together.
curl -skIL https://example.com/Different from domain error; sw-cp-server, sw-engine, and /var/log/plesk/panel.log are checked.
There is no single reason. .htaccess incompatibility, PHP fatal error, memory limit, FastCGI timeout, and permission issues are the most common groups.
No. It is a security risk and hides the ownership issue. Plesk's expected ownership and permission structure should be preserved.
Find and optimize which URL and code is consuming memory. If the load is really high, a controlled increase in server capacity may be made in line with the server capacity.
Backup can be used for temporary diagnosis; however, security, permalink, and redirection rules will be disabled, so it is not a permanent solution.
On Linux, the error_log and proxy_error_log files are usually located at /var/www/vhosts/system/alanadi/logs/. They can also be viewed from the Domains > Logs screen in the panel.
Incompatible code can be fixed, but random version changes may introduce new issues; application and extension requirements should be checked.
Verifies Plesk's file system integrity and ownership structure. Output command results should be carefully examined in production.
By analyzing cPanel, WHM, CloudLinux, LiteSpeed, MariaDB, Exim and security layers together, we fix the root cause of the failure instead of just removing the service.