-
Hello, I did make a reddit post, but will post the contents in here: After deploying the stack I get the following log for each qbittorrent and gluetun containers (I have a subscription to Surfshark). I also took preliminary steps to portforward the ports specified in the ports section under the Gluetin yaml section in the Synology firewall. Using my local IP address with port 8080 (i.e https://[nas_ip_address]:8080). I ran the systemd script following these steps: https://github.com/qdm12/gluetun/wiki/Synology-prerequisites Still is unable to access the UI. I have been messing around with this all day, and can't seem to find anyone else having a similar problem. This feels like a dumb issue since everything seems to be running successfully. I have followed on many tutorials on how to set this up, and tried all of their variations: https://www.youtube.com/watch?v=xbSfaKwyfXE&t=274s I tried following along this write up, but did not understand my use case with this setup. Also since my devices are under the same subnet: https://www.reddit.com/r/synology/comments/sluiga/guide_using_vpn_with_docker_containers_on_dsm_7/ Please note: I do successfully run qbittorrent WITHOUT gluetun. UPDATE: I did find this post which indicates this as a known bug, but does not seem to indicate an adequate solution. Even after mapping the ports, still unable to access the UI Here is my Docker-Compose.yml file:
Log file for Qbittorrent container:
Log for gluetun container:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
This should work i think, that's odd. |
Beta Was this translation helpful? Give feedback.
This should work i think, that's odd.
Try maybe with a custom bridged docker network, and attach gluetun to it? Maybe the default bridge network doesn't work for properly. Let me know if you need help doing that. Keep in mind I'm currently moving homes so I'm very much laggy for the next 2 weeks.