How To Set Up My Website With NAT VPS Print

  • 123

In order for your website to be publicly available with a SiteHUB NAT VPS, we need to proxy your VPS port. You can easily achieve this yourself from the management control panel for your VPS.

  • You would need to select the VPS you want to manage from your VPS list by clicking the arrow in the far right.
  • Once inside the management console, click on the Domain Forwarding button to bring up the dashboard.
  • You will have access to ports 10,000-20,000. If a port is already in use, you will get an alert letting you know so and would need to pick an alternative port number except for the case of reserved ports which will allow as many users to map to it via their domain name.
  • Click on the Add tab
  • Select the protocol. For domain forwarding, select HTTP/S, for all other application and SSH ports, select TCP.
  • Select the source domain/IP. For HTTP/S protocols, you will need to enter the domain name you wish to use. You would need to set an A record in your DNS zones for the domain to the host IP for the site to become available.
    For TCP, you would need to set the host IP as the source. This would be automatically populated.
  • For HTTP/S protocol, the ports will automatically populate.
    For all other protocols, enter the hosts' source port between ports 10,000 to 20,000
  • Enter your VPS Destination IP. This will also be auto-populated.
  • Now, enter the VPS destination port e.g 22 if you wanted to open SSH access.
  • Click ok for the configuration to be saved. The port will be available immediately.

At this point, you would want to alter your DNS zones and add an A record to the domain provided pointing to the host server's IP. The IP can be found in your VPS panel.

After completing the DNS configurations, your site should be resolvable.

If your control panel requires alternative ports e.g 8080, then open the port in the domain forwarding proxy e.g 12000, provide a hostname for HTTP/S forwarding and set the A record then your site and panel will now be accessable.


Was this answer helpful?

Back