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

Moving the Panel from the maindomain.tld:port to sub domain?

JustinGivens

Basic Pleskian
Not sure if this is possible but I would like to move the default panel location to a sub domain with that port required.

Example: panel.maindomain.tld:8443

My idea is that the panel wouldn't load if someone went to maindomain.tld:8443. They would also need to know the sub domain as well. Just better security if you ask me.

Is this even possible? I've searched the internet, kb and forum and couldn't find anything.
 
I'm going to go with possible, but you'd have to configure the panel's underlying lightppd server to do this, the thought of which makes me dizzy! (Not to denegrate lightppd but I'm starting to learn nginx alongside apache and the idea of the third web server configuration syntax doesn't fill me with joy).

I think its far better if you can control the IPs from which you connect to the panel and then restrict administrative access to that IP (alongside firewalling if there's only you connecting), then you're not relying on obscurity.

Paul.
 
Back
Top