Secure Global Desktop Administration Guide > Security > Users are unable to connect to Secure Global Desktop when it is in firewall forwarding mode

Users are unable to connect to Secure Global Desktop when it is in firewall forwarding mode

Users may find that they are unable to connect to Secure Global Desktop when it is in firewall forwarding mode. A common cause of this problem is that Secure Global Desktop was started before the Secure Global Desktop Web Server.

In firewall forwarding mode, Secure Global Desktop listens on port 443 and forwards any web connections to the Secure Global Desktop Web Server, which is configured to listen on localhost port 443 (127.0.0.1:443). If Secure Global Desktop is started before the Secure Global Desktop Web Server, Secure Global Desktop binds to all the available interfaces and this means that Secure Global Desktop forwards any web connections to itself in an infinite loop.

One solution is to always start the Secure Global Desktop Web Server before Secure Global Desktop.

Another solution is to configure Secure Global Desktop so that it never binds to the localhost interface. To do this, run the following command:

tarantella config edit \
  --tarantella-config-server-bindaddresses-external "!127.0.0.1"

Note On some shells you cannot use double quotes ("!127.0.0.1") as the !127 may get substituted. Use single quotes instead ('!127.0.0.1').

You can also use this command to specify exactly which interfaces you do want Secure Global Desktop to bind to. You do this by entering a comma-separated list of DNS names and/or IP addresses.

Related topics
Using Secure Global Desktop with firewalls Using Secure Global Desktop with the HTTPS port through a firewall