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

Sitebuilder and Plesk Panel behind Firewall

S

synergypro

Guest
Can someone answer a configuration question for me. Support has been totally useless, they've been screwing around for over a week and seem to have no clue. They can tell me what the problem is but are unable to tell me how to fix it.

When I have Plesk Panel configured to work behind a firewall (Web Hosting Settings IP Address is the internal address of 192.168.102.7) as described in documentation my site is visiable by the public using the public IP address. However in this configuration, Sitebuilder is not able to publish the site or "Verify Location".

When I setup the site in Plesk to use the Public IP address in the Web Hosting Settings, Sitebuilder is able to "Verify Location" and publish the site. However when trying to access the site using the public URL / IP the user is shown the "Default Plesk website" and not the specific site.

One workaround support did was to MANUALLY add an entry to /etc/hosts for the internal IP / domain name. However that's not acceptable because I don't want to add an entry everytime someone creates a domain.

Any suggestions?
 
Back
Top