• 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.

Recent content by powerAG

  1. P

    Question Plesk login 8443 cannot be called up

    I hope I have done everything right ? I didn't intend to restart anything and restarted the whole server yesterday. Nothing else was done. root@hostname:~# uptime 18:00:45 up 20:47, 1 user, load average: 0,19, 0,09, 0,02 root@hostname:~# service sw-cp-server status ● sw-cp-server.service -...
  2. P

    Question Plesk login 8443 cannot be called up

    Thanks for the feedback! I just uninstalled imunify360. However, the problem still persists. That's what he gave me with both commands. root@hostname:~# service sw-engine status ● sw-engine.service - Startup script for Panel sw-engine Loaded: loaded...
  3. P

    Question Plesk login 8443 cannot be called up

    I think I have found the error, a friend recently installed imunify360 for me. Could this be the reason? But how do I deactivate it or add the IP to the whitelist?
  4. P

    Question Plesk login 8443 cannot be called up

    okay, i did it and it doesn't seem to be the problem. It seems to be the problem with the port blocking, I found a guide on the internet, but it is still blocked. I had not set anything to be blocked. Is there a way to unblock the port again, or so that I can log in again? I can't explain...
  5. P

    Question Plesk login 8443 cannot be called up

    Hello, I am new and hopefully someone can help me here. I have a Debian 12 server with Plesk Obsidian. My server updates automatically, so apparently Plesk updated itself and the server was restarted by the hoster at some point. (Hardware swap) I had last customized the hostname and the...
Back
Top