

No, the compose file lists the network but the container is still in its own network.
You need to add this to the container
networks:
- nginx-proxy-manager_defualt
I run horwood.cloud
Could you help fund my server 👉 Fund me
No, the compose file lists the network but the container is still in its own network.
You need to add this to the container
networks:
- nginx-proxy-manager_defualt
side note, I would expose traefik on 127.0.0.1
if its on the same host as nginx. as traefik is visible on all network interfaces.
‘traefik.http.routers.nightscout.rule=Host(
localhost
)’
so traefik will be looking for the host header localhost
and only route requests to the service if it matches, sh when you use your real domain that should be what you use as the host header from nginx
Hello
could you update this with your compose file please?
my first guess is that maybe traefik does not know about nightscout or nightscout is still listening on its own ports
You need to be visible on the internet, if my instance can’t see you then I can’t send you updates
2-3Gbps? Mate, I can only get 40Mbps here. I would kill for that bandwidth!
OVH is not free, but very cheap