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

Trouble with NAT

A

askar

Guest
Is any one using sitebuilder behind NAT?

I am having problem as some of place it showitng internal ip to public like to view trail site etc.

Can any one help how to fix it?

Thanks,
Ali
 
no one using it behind NAT?

please help if any one using behind firwall.

Thanks,
Raza
 
Thanks Alex,

I am going to look for FTP but from site wizard I am having problem too. its working fine but on last step before publishing it searching internal IP and not finding it and failed to view the page and publishing trail site it also adding internal IP to view trail published site and again failed as internal IP.

I found below KB on swsoft but really dont understand exactly what is binding and how to modify it.
http://kb.swsoft.com/article_174_1341_en.html

I will be very helpfull if you clear what is binding and how to chagne it.

right now I have dadicated IP for site builder on port 80 and no header defined.

I appriciate your help in this regard.

Thanks,
Raza
 
Did you find [Install dir]\Hosting Srevice\bin\HostingService.exe.config file on your server? If so please open it in some text editor (notepad or something like this) and find follwing section:

<!--
<add key="PreconfiguredUrl" value="http://localhost/wsb/sbpreview"/>
-->

As you can see it is commented with <!--........--> symbols. Try to replace this section with following one:

<add key="PreconfiguredUrl"
value="http://yourserver.com:80/Sites" />
</appSettings>

http://yourserver.com - it can be your server name (which should be resolved correctly) or external IP address.
After applying changes you need to restart Sitebuilder's services:

net stop SBPreviewHost
net stop SBUpdater
net start SBPreviewHost
net start SBUpdater
Restart Sitebuilder site's application pool
 
Back
Top