• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

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