hmmm. I fired up grafana, homeassistant, influx, and other similar services behind the same traefik instance. Each one gets a secure SSL in the browser at https://subdomain.mydomain.com.
Traefik reads the config of the container, you just put a label telling it what path to listen to, and it gets the SSL from lets encrypt automagically. It just works, ssl-terminated subdomains pop up in seconds. Except for node-red. It takes the request on port 80 of the subdomain, upgrades it to https and forwards it to the right container. Everything works, just shows insecure still (but with a valid cert?)
The whole cert path appears to be present, if I look up the path in the browser it shows the DTS Root CA X3, then the Lets Encrypt Authority, then the cert
In Home-Assistant, you have to put some extra lines in the config for it to play nicely with an ssl termination proxy, like this:
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
I'm just wondering if there are environment variables or anything I need to do to node-red to have it behave like the other services?