Solving LAN-WAN Recognition Problems

Organizr is capable of recognizing whether the connecting IP address is a WAN or LAN IP address such that depending on that either the Tab URL, or respectively the Tab Local URL will be used.

It is clear that Organizr, depending on how it is accessed, must always receive the connecting address, such that in case proxies are involved, the appropriate headers must be passed such that Organizr will be able to tell from which network a browser connects from.

For example, given the caddy reverse-proxy, the following configuration will pass the headers to Organizr listening on the local machine:

        redir /services /organizr/
        redir /organizr /organizr/
        handle_path /organizr/* {
                rewrite /organizr* /{uri}
                reverse_proxy 127.0.0.1:5000 {
                        header_up Host {host}
                        header_up X-Real-IP {remote}
                        header_up X-Forwarded-Host {hostport}
                        header_up X-Forwarded-For {remote}
                        header_up X-Forwarded-Proto {scheme}
                }
        }

Typically, the symptoms of a non-working setup is the situation where all the services work if they are configured with Tab URL and Tab Local URL being set to the external IP address such that connecting with a local client does not load the services as well as the reverse case where Organizr is configured with Tab URL and Tab Local URL set to the local address and loading the services externally does not work.

Fortunately, Organizr detects headers such as X-Forwarded-For or X-Real-IP such that setting them and passing them to Organizr is necessary.