This is on a pretty fresh install of the Graylog 3.1.3 OVA appliance install, which mean it runs nginx (most of the google results for this issue apply to apache on docker).
Everything works great internally, but not externally. It’s exposed to the internet via the fantastic Nginx Proxy Manager by jc21 ( https://github.com/jc21/nginx-proxy-manager )
I also tried adding the IP of the Nginx Proxy Manger to the trusted_proxies line in the server.conf to no avail. Then I took a stab at messing around with nginx config files by changing some headers, but the same type of issues persisted, once it became accessible externally it stopped being accessible internally, and vice versa. It might not even be the Nginx Proxy though, I port forwarded the graylog server directly out to the internet, and same issue happens, the “blank” index page had resources linked with absolute paths to the internal IP and not relative paths.
So what is going on here? Why is it changing bind address internally when the setting I changed was http_EXTERNAL_uri ? Why is it sending the internal bind address when being accessed outside? Or I guess, why it is generating absolute paths? I will admit web servers are not a strong suit of mine, but I’m not having this issue with 10+ other apps being proxied through Nginx Proxy Manager.