• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is 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.

SMTP Server And Control Panel Switched Off?

C

creb

Guest
Hello,


This day my website was really slow. I connected to plesk and saw the usage of CPU was at 99%.
I decided to reboot the server.

Once it restarder it showed things like:
Problems found:
The Plesk Control Panel service is switched off.
Solutions:
Restart the Plesk Control Panel service.
The SMTP server service is switched off.
Solutions:
Restart the SMTP server service.

I applied the solutions but it changed anything. When applied it loads then come back to the same point with the same problems.
I already stopped and restarded container without any effect.

By the way, I can't access anything, when clicking on SERVER, I have no menu, it shows directly the problem and ask me to apply for solutions.
Same thing when clicking on CLIENTS or DOMAINS.

The only thing I can access is virtuozzo.



Do you have an idea how to solve this?
 
Hello

The problem seems not in SMTP service, but in Plesk installation itself. If you can access hardware node
with Virtuozzo try to disable offline management for the container with
vzctl set CTID --offline_management no --save
Then check which error message is displayed when accessing Plesk CP. Or you can access Plesk CP without
access management at http://server_IP:8880. This will be the real error message which is the reason of the issue.
Also you can analyze log files /usr/local/psa/admin/logs/httpsd_error_log for possible error messages.
 
Back
Top