• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Disable Port 8443 when you use a hostname (Plesk Obsidian)

vaelu

Basic Pleskian
Hello Pleskians!

Since Plesk Obsidian is out, it is possible to access the Plesk interface over a hostname without entering the port 8443 (How to make Plesk interface accessible over a hostname without entering the port number). We have activated this feature and that it isn't possible to connect over 8443 and also not over hosted domain names, we deactivated the port 8443 with our firewall. It does work, but my question is, it this clean?

Since I get errors when I check the Apache error log with "plesk log error_log", I don't think that this is a good solution. Is there any other solution for this?

Code:
2020/04/12 06:38:50 [emerg] 24914#0: bind() to 0.0.0.0:8880 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to [::]:8443 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to [::]:8880 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to 0.0.0.0:8443 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to 0.0.0.0:8880 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to [::]:8443 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to [::]:8880 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to 0.0.0.0:8443 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to 0.0.0.0:8880 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to [::]:8443 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: bind() to [::]:8880 failed (98: Address already in use)
2020/04/12 06:38:50 [emerg] 24914#0: still could not bind()

Thanks in advance.
 
Last edited:
this works flawlessly for me.
This was not the questions. We already use a custom URL through this way. But Plesk is still accessible through port 8443, and we want to deactivate this that Plesk in only reachable on the custom domain.
 
Back
Top