Last edited:
I can access the docker without issues from the LAN for example https://IP_SYNOLOGY:8080 gives me the qbittorrent web UI which runs inside a docker, or https://IP_SYNOLOGY:5001 gives me the DSM management.Do you have firewall rule that allows for docker subnet to “talk” to your host (nas) subnet? Or maybe you have a fw rule that blocks it?
Then I set up on my router port forwarding to ports 8080 and 5001.
Then when accessing from the interner, https://MY_EXTERNAL_IP:5001 works ok, but I cannot connect to https://MY_EXTERNAL_IP:8080.
But when I do a open port checker, for example Open Port Check Tool - Test Port Forwarding on Your Router, on ports 8080 and 5001, they are both open. But when accessing 8080, it gives me no response, no data.
In firewall I have SOURCE:ALL PROTOCOL:ALL PORTS:8080,5001 Allow
PS: it works now. Is it possible that it does not work on ports that are assigned/forwarded via the web station?
PS2: Now i see another issue : is it possible to configure docker in a way, that the containers do not have access to my LAN (192.168.x.x), but still have access to the internet? Like make then isolated from my LAN.