• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Resolved I can not login into plesk

elenmylo

New Pleskian
Server operating system version
CentOS 7 Plesk 18 (Obsidian)
Plesk version and microupdate number
CentOS 7 Plesk 18 (Obsidian)
I am getting
This page is not working cannot process this request at the moment.
HTTP ERROR 500
 
Oh man, I've been there before. That HTTP 500 error can be a real pain. Here's what I did when I faced something similar on my CentOS 7 server with Plesk 18 (Obsidian):
Check Logs: I started by looking at the logs. Plesk keeps its logs in /var/log/plesk/panel.log, and for the web server, it's either /var/log/httpd/error_log for Apache or /var/log/nginx/error.log for Nginx. These files can give you some clues about what's going wrong.
Permissions: I made sure all the file and folder permissions were set right. Sometimes, if they're off, it can cause issues.
Disk Space: I checked to see if my server's disk was full. A full disk can cause all sorts of weird problems.
Restart Services: I tried restarting the Plesk and web server services. You can do this with these commands:
bash
service psa restart
service httpd restart # For Apache
service nginx restart # For Nginx
Check for Corrupted Files: I ran Plesk's repair utility to see if there were any corrupted files. You can do this with:
css
plesk repair all -y
PHP Settings: I checked my PHP settings and the PHP error log to see if there were any issues there, especially if I had made any recent changes.
Disable Extensions: I had some third-party extensions installed, so I tried disabling them to see if that fixed the issue.
If none of that works, it might be time to reach out to Plesk support or your hosting provider for some extra help.
 
Back
Top