With a web browser, if we try to access the web UI behind the Traefik reverse proxy on the testbed, we have a blank page because the webapp is not designed to work behind a reverse proxy. However, a reverse proxy is required for communication security, i.e. SSL/TLS protection. You can test it with an Apache or NGINX (with SSL enabled) instead of Traefik to reproduce the issue outside the testbed.
cdanger
commented
5 years ago
With a web browser, if we try to access the web UI behind the Traefik reverse proxy on the testbed, we have a blank page because the webapp is not designed to work behind a reverse proxy. However, a reverse proxy is required for communication security, i.e. SSL/TLS protection. You can test it with an Apache or NGINX (with SSL enabled) instead of Traefik to reproduce the issue outside the testbed.