Some additional requirements using external reverse proxy #4426
Description
Probably a niche gotcha, but when adding optional services, or changing default user/path options which require/recommend also creating a CNAME record for custom user/service, then:
if using an external reverse proxy setup pointing to traefik inside the containers - alongside needing to create a CNAME for the custom user/service, it is also necessary to update the server name: to include same in proxy config on webserver.
i.e adding fluffychatWeb service needs both CNAME in DNS, and fluffychat.example.com in webserver conf server name: block, to correctly forward (and wildcard CA). EDIT It does kind of suggest this in a comment in the sample nginx.conf, but could be clearer for the inexperienced!
Also experiencing TLS send failures (expired cert/STARTTLS fail) with postmoogle, suspect this is also due to reverse proxy setup disabling traefik_config_entrypoint_web_secure_enabled: false to avoid 443 conflicts, which also disables TLS in traefik. Trying aux role here will confirm if successful fix.
This is a vast and wonderful project - just discovering how evolved the ecosystem is after tinkering with it several years ago. Way easier with this!