Arch Linux

Jack_CM

Member

Registered: 2012-02-10

Posts: 55

Connection problem to my dockers outside my LAN

Hello,

I hope this is the right place to ask for this strange problem. I've set up an home server with Arch Linux as OS. I installed docker and configured swag, airsonic, nextclould and duckdns.

So far so good as I tested them from my LAN by typing in the web browser, for instance, <my-nextcloud-name>.duckdns.org and I can access it without any problem. The only small issue was that I had to play around with IPv6 in my router as my ISP IPv4 is a NAT..behind another NAT so there is no way to open the ports (they allow you for a fee however). But in any case, I was able to open the 443 and the optional 80 port for my IPv6. (I checked with some external website like http://www.ipv6scanner.com/ and indeed they are open).

However, as soon as I leave my house and try to connect to my nextcloud or airsonic through my mobile connecton or my workplace network I cannot and I 'm really struggling to understand why. If it helps, this is how I set up the docker swag:

# docker create \
  --name=swag \
  --cap-add=NET_ADMIN \
  --network my-net \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Europe/Zurich \
  -e URL=duckdns.org \
  -e SUBDOMAINS=<my subdomains are here> \
  -e VALIDATION=http \
  -e DUCKDNSTOKEN=<my token> \
  -e EMAIL=<my email>\
  -e ONLY_SUBDOMAINS=true\
  -p 443:443 -p80:80 \
  -v $HOME/AppData/swag:/config \
  --restart unless-stopped \
    ghcr.io/linuxserver/swag

As a side note, if I set

-e ONLY_SUBDOMAINS=false

then I get some firewall error to get the certificates, not sure if this is relevant but I am not really sure I understand what that option means. Also I checked the logs and I don't see anything suspicious.
I also enabled IPV6 for docker as suggested in the wiki

I hope is not something messed up with my router / ISP but I am open to any suggestions!