Secure Global Desktop 4.40 Administration Guide > Security > Users Cannot Connect to an SGD Server When It Is In Firewall Forwarding Mode

Users Cannot Connect to an SGD Server When It Is In Firewall Forwarding Mode

If users cannot connect to an SGD server when it is in firewall forwarding mode, this is usually caused by starting the SGD server before the SGD Web Server.

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

One solution is always to start the SGD Web Server before the SGD server.

Another solution is to configure SGD so that it never binds to the localhost interface. To do this, use 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 might be substituted. Use single quotes instead ('!127.0.0.1').

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

Related Topics
Using SGD With Firewalls