• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Plesk: no response

J

james_times

Guest
I have a lot of problems with my new dedicated server. First, SMTP crashes on its own every a couple of hours. Then, I cannot even start Plesk after the server is rebooted for more than 4 hours. No response at all. Pleask stucks forever. Sometimes database crashes too but will be restarted automatically. However, the server is still running.

The web traffic is constently low on my server and there is no peak. The memory usage is almost 100%, but I dont have any extra program on the server. Just the basic things like SMTP, DNS, Database, etc. I have a server with 512MB memory. Can this be the problem?

Is there any solution?

Since I cannot use Plesk (unless I request a server reboot, which I cannot do fro every a couple of hours!), I cannot restart SMTP through Plesk. Before I have any solution, is there any alternative way that I can restart the SMTP service on the server?

Thanks for any help!
 
Back
Top