• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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