LongReach Ports
6560 – LongReach Manager
6561 – LongReach Console
6563 – LongReach HTTP Server
6564 – LongReach HTTPS Server
LongReach Internal use
6560 – LongReach Manager
6561 – LongReach Console
• The LongReach server does bind to ports 6560 and 6561, but does not accept TCP/IP connections on these ports.
• The following manager.properties keywords disable accepting TCP/IP connections on these ports.
o tcp.client.address=*none
o studio.client.address=*none
o console.client.address=*none
• Note: YOU MUST NOT OPEN PORTS 6560 and 6561 TO PUBLIC ACCESS.
LongReach External use
6563 – LongReach HTTP Server
6564 – LongReach HTTPS Server
• Only 1 port needs to be opened to the public. This is the LongReach HTTP Server port 6563.
• The LongReach HTTPS Server port 6564 is not configured to be active, so is not used.
• It is possible to configure LongReach to have both a HTTP and HTTPS instance running, so both ports can be used.
• It is possible to change the default configuration to use HTTPS only and now port 6563 is not being used and port 6564 is being used.
Footnote
• With LongReach, it is actually possible to open no more ports and just use an existing port 80.
• Change LongReach port value 6563 to 80. This assumes that port 80 is not used on the same machine.
• You could also use a reverse proxy
• Mobile Device ---> port 80 ---> Reverse proxy ---> port 6563