Common Queries: Plesk FAQs

a) I enabled access to Plesk via HTTPS using a 443 TCP port. How do I turn off access to Plesk via TCP port 8443 ?

Plesk cannot disable access to the 8443 TCP port, but adding a rule to the operating system firewall can prevent incoming connections.

b) I want to change the domain that accesses Plesk through the 443 TCP port. How do I change it in the Plesk interface ?

You can find more information on the Plesk website or contact our technical support for help.

c) I updated Plesk Onyx to Plesk Obsidian, but I still cannot log into Plesk without specifying the 8443 TCP port. What do I do ?

You can find more information on the Plesk website or contact our technical support for help.

d) Crashed Plesk services are now automatically restarted on supported system-based Linux distributions. Is it possible to configure restart properties in Plesk ?

Absolutely not

e) What features are enabled by default in Plesk Obsidian ? Do I need to enable them manually after updating to Plesk Obsidian ?

The features that are automatically enabled on a new Plesk Obsidian installation are listed below:

• Apache Graceful Restart is now robust enough to be set as the default to minimize website downtime.
• The system utilizes SPF, DKIM, and DMARC for both incoming and outgoing email communication.
• ModSecurity and Fail2Ban version 0.10 are now operational immediately.
• Newly created websites are automatically enabled with an SEO-friendly HTTP > HTTPS redirect.

Upon upgrading your server from a previous Plesk version to Plesk Obsidian, the listed features will remain unchanged. If any features were not enabled before the update, they must be manually enabled if necessary.