I’ve had my synology ds 218+ for a while now and have slowly started to tinker with it more and more. I started just using syno community packages and official apps but have increasingly moved to have almost everything in docker. Spent a lot of time trying to learn how to use docker and I’m at the point where I have most things running as I’d like - e.g. sonarr, radarr, Calibre web, organizr, etc.
Recently I’ve been trying to make my setup more secure and efficient so I’ve been trying to more from using the in build application portal reverse proxy to access my apps to something like traefik or caddy so I can go through organizr and then use authentication to access all other apps.
Started with traefik but I had issues adding labels to containers as I believe DSM uses an old version of docker and the links i have setup there don’t play well with portainer, plus I figured I wouldn’t be able to add labels again easily each time the container image updated.
So I’ve moved to caddy. I have this setup in docker with a basic Caddyfile that someone on the caddy community has had a quick look at and sees no issues with. My problem is that I don’t think that traffic is reaching caddy at the moment. I’ve removed all my existing application portal setup and have forwarded ports 81/444 from my router to my NAS ip using the same ports. These are defined as the local ports on my caddy docker container and also allowed in my router and DSM firewalls.
I’m using the built in synology ddns but when I try to access xxxx.synology.me/sonarr for example this redirects me to the DSM login on port 50005 (I have the option to redirect to https in DSM enabled).
I can’t for the life of me figure out why traffic isn’t hitting caddy when I believe the ports all line up, don’t think it can be a firewall issue as the traffic gets through to th3 DSM login.
Any help from anyone running an alternative reverse proxy in docker would really be appreciated as at the moment I’m completely stuck.
Recently I’ve been trying to make my setup more secure and efficient so I’ve been trying to more from using the in build application portal reverse proxy to access my apps to something like traefik or caddy so I can go through organizr and then use authentication to access all other apps.
Started with traefik but I had issues adding labels to containers as I believe DSM uses an old version of docker and the links i have setup there don’t play well with portainer, plus I figured I wouldn’t be able to add labels again easily each time the container image updated.
So I’ve moved to caddy. I have this setup in docker with a basic Caddyfile that someone on the caddy community has had a quick look at and sees no issues with. My problem is that I don’t think that traffic is reaching caddy at the moment. I’ve removed all my existing application portal setup and have forwarded ports 81/444 from my router to my NAS ip using the same ports. These are defined as the local ports on my caddy docker container and also allowed in my router and DSM firewalls.
I’m using the built in synology ddns but when I try to access xxxx.synology.me/sonarr for example this redirects me to the DSM login on port 50005 (I have the option to redirect to https in DSM enabled).
I can’t for the life of me figure out why traffic isn’t hitting caddy when I believe the ports all line up, don’t think it can be a firewall issue as the traffic gets through to th3 DSM login.
Any help from anyone running an alternative reverse proxy in docker would really be appreciated as at the moment I’m completely stuck.