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

Cann't login to 8443 (!?)

H

happyuser

Guest
Hello,

My provider installed the newest Plesk 7.5.3. on my Suse (https://213.131.237.43:8443/)

Everything worked excellent. I configured everything : SSL, Firewall, Domains.

But when I rebooted the server, I can't no longer login to Plesk: https://213.131.237.43:8443/

I can visit the domains, even SSL Domains. But not Plesk (!!).

I already tried:

cd /usr/local/psa/admin/bin
./httpsdctl start

But - no result.

Please help me !!

Thanks!!

P.S. I am not sure, but I think it is not possible to block this port with the firewall i configurated with plesk?
 
To verify it's not the firewall just run:

service iptables stop

... via ssh.
 
# find / -name "firewall"

/usr/local/psa/etc/modules/firewall
/usr/local/psa/var/modules/firewall
/usr/local/psa/admin/plib/modules/firewall
/usr/local/psa/admin/plib/templates/modules/firewall
/usr/local/psa/admin/htdocs/modules/firewall
/usr/local/psa/admin/bin/modules/firewall
/usr/local/psa/admin/sbin/modules/firewall
 
Thanks !!

I found the problem indeed in the firewall. The port was blocked!
 
Back
Top