Search results

Of course this behavior didn’t exist years ago, back in the Onyx days or earlier. It has been introduced as a “feature” in some version of Obsidian, since I’ve seen that the default behavior of this setting actually changes depending on whether the server was upgraded or freshly installed...

By the way, Plesk documentation doesn’t mention that here https://docs.plesk.com/en-US/obsidian/administrator-guide/plesk-administration/ports-used-by-plesk.64950/ which makes the whole situation even more misleading. It becomes kind of a joke when the docs don’t explain that “admin access”...

To me continues to have no sense. Plesk lets you set “Allow administrative access only from certain IPs” — but that only applies to port 8443. Meanwhile, by default, the admin interface is also exposed on https://serverip/ via port 443, because in Tools > Customize Plesk URL, the setting is...

Plesk Obsidian 18.0.68 Web Host Edition here. I'm reporting a major security and design inconsistency in how Plesk handles access control for the admin interface. As part of the basic hardening process, I ensured that only essential ports — 80 and 443 — were exposed, as expected for a standard...

So, still no update on this?

Sorry for the intrusion, but wouldn't it be better for all to post english Plesk's screenshots (instead german) so that this thread can help as many people as possible? English is the standard for IT so it should be taken as reference.

Me too would like to answer the questions posed to Automata. Really you're asking "why it's so critical"? A failover is critical in thousands of activities that cannot accept downtime (big e-commerce stores, hospitals, event booking... and so on, there are thousands of thousands of businesses...

Unbelievable.

Thanks!