KB: Using Popular Ports with The Web Interface

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Revision as of 16:34, 6 November 2009 by Reno (talk | contribs) (Created page with '==Introduction== Using the Commit Web Interface, you can only configure ports above 1000. This rule is in place in order to prevent other servers from taking up the port you've s…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Introduction

Using the Commit Web Interface, you can only configure ports above 1000. This rule is in place in order to prevent other servers from taking up the port you've set for the Commit Web Interface. This may pose a problem if you wish to use more popular ports such as 80 or 443, for web surfing.


Resolution

The Commit Web Interface requires the use of ports 1024 or higher in order to properly function. Since you may have many clients with restricted browsing capabilities, we would suggest that you set your corporate firewall to translate the external port 443 or perhaps even port 80 to the current Web Interface port (4961?) for that server using NAT (Network Address Translation).

Before making these adjustments, you should verify that nothing else expects connections on the selected port (80?) on your Firewall, and you should also make sure alter the login page on your web site (In case you have embedded the Web Interface login page or a link to it anywhere), and change the port to the relevant one once the NAT rule set in your external firewall.