Closed kajvans closed 3 months ago
@qdm12 is more or less the only maintainer of this project and works on it in his free time. Please:
Be careful exposing your credentials as you did. I removed them for you.
Thanks @frepke !
@kajvans I'm not sure what produces site cant be reached
, I guess that's one of your other containers? Is this in your browser? What service are you trying to access that gives you site cant be reached
. Alternatively you can try having the other containers in the same docker-compose.yml and use network_mode: "service:gluetun"
?
sabnzbd and qbittorrent both give the same error. Also when trying to run it in the same compose file nothing changes
sabnzbd and qbittorrent both give the same error. Also when trying to run it in the same compose file nothing changes
Are you on a OpenMediaVault box? If yes, don't use UID 998 and GID 100.
How do you try to connect to the web interface of SABNZBD, <server-ip>:port
Can you also post the combined compose-file
version: "3"
services:
gluetun:
image: qmcgaw/gluetun
container_name: gluetun
cap_add:
- NET_ADMIN
networks:
- services
environment:
- PUID=998
- PGID=100
- TZ=Europe/Berlin
- VPN_SERVICE_PROVIDER=expressvpn
- OPENVPN_USER=
- OPENVPN_PASSWORD=
- SERVER_COUNTRIES=Netherlands
- FIREWALL_VPN_INPUT_PORTS=57786
volumes:
- /srv/mergerfs/config/appdata/gluetun:/gluetun
ports:
- 8086:8000/tcp
- 8080:8080 # SABnzbd WEB GUI
- 8081-8085:8081-8085 # qBittorrent WEB GUI
- 6881-6885:6881-6885/udp
- 6881-6885:6881-6885
- 8888:8888/tcp # HTTP proxy
- 8388:8388/tcp # Shadowsocks
- 8388:8388/udp # Shadowsocks
restart: unless-stopped
qbittorrent:
# latest version has a memory leak on Debian/Ubuntu by the looks of it
image: lscr.io/linuxserver/qbittorrent:14.3.9
container_name: qbittorrent
network_mode: service:gluetun
environment:
- PUID=998
- PGID=100
- TZ=Europe/Berlin
- WEBUI_PORT=8082
volumes:
- /srv/mergerfs/config/appdata/qbittorrent:/config
- /srv/mergerfs/pool/share_media/:/data
restart: unless-stopped
sabnzbd:
image: lscr.io/linuxserver/sabnzbd:latest
restart: unless-stopped
network_mode: service:gluetun
container_name: sabnzbd
environment:
- PUID=998
- PGID=100
- TZ=Europe/Berlin
volumes:
- /srv/mergerfs/config/appdata/sabnzbd:/config
- /srv/mergerfs/pool/share_media/:/data #optional
- /srv/mergerfs/pool/share_media/incomplete:/incomplete-downloads
networks:
services:
external: true
I try to access it by ip:ports And why shouldn't I use uid 998 and gid 100
When it's an OMV machine, UID 998 is the OMV admin user. It gives you user and permission issues (you can read a lot of this mistake on the OMV forum). In OMV you can create a new user for your docker-containers if you want.
so i should just remove it?
No, create a new user and use the UID and GID from that user.
Oke I will, but that is not the reason that I first could access containers behind gluetun and now not. Did not change anything in the container only installed a fresh os so maybe the firewall problem but that is also weird because my computer has completed access and also all the ports are open
Not sure if this problem has anything to do with Gluetun. I run 3 different servers, all Ubuntu and using Gluetun + socks5, all configured in the same compose file. It's been working flawlessly since I started using it way back. Today though, I ran a apt-get upgrade and the following packages was updated "docker-buildx-plugin docker-ce docker-ce-cli docker-ce-rootless-extras docker-compose-plugin" on all 3 servers. Now all of a sudden I can't reach any of my socks5 servers on these 3 servers. Haven't had the time to investigate further, but thought I might put it out there for you to know.
Oke so it is a problem with newer versions of docker. So sort of a problem with gluetun (I think)
That's weird, I've all updated to the latest and never have this issue on my server. I run everything in one combined compose file with Surfshark.
This is my compose-file:
x-service-common: &base-service
network_mode: "service:gluetun"
depends_on:
gluetun:
condition: service_healthy
environment:
- PUID=1000
- PGID=100
- TZ=Europe/Amsterdam
restart: unless-stopped
services:
gluetun:
image: ghcr.io/qdm12/gluetun:latest
container_name: gluetun
hostname: gluetun
cap_add:
- NET_ADMIN
ports:
- 14800:8000/tcp # HTTP control server
- 14801:8888/tcp # HTTP proxy
- 14802:8388/tcp # Shadowsocks
- 14802:8388/udp # Shadowsocks
- 14810:8080/tcp # sabnzbd
- 14811:5076/tcp # hydra2
- 14817:8112 # deluge
- 14818:6881 # deluge
- 14818:6881/udp # deluge
volumes:
- /dockercfg/gluetun:/gluetun
environment:
# VPN Configuration
- VPN_SERVICE_PROVIDER=surfshark
- VPN_TYPE=wireguard
- WIREGUARD_ADDRESSES=10.14.0.2/16
- WIREGUARD_PRIVATE_KEY=<REDACTED>
- SERVER_COUNTRIES=Netherlands
# DNS over TLS
- DOT=on
- DOT_PROVIDERS=cloudflare
- DOT_CACHING=on
- DOT_IPV6=off
- DOT_VERBOSITY=1
# Firewall
- FIREWALL=on
- FIREWALL_DEBUG=on
- FIREWALL_OUTBOUND_SUBNETS=x.x.x.x/24
# Shadowsocks
- SHADOWSOCKS=on
- SHADOWSOCKS_LOG=off
- SHADOWSOCKS_LISTENING_ADDRESS=:8388
- SHADOWSOCKS_CIPHER=chacha20-ietf-poly1305
# System
- TZ=Europe/Amsterdam
- PUID=1000
- PGID=100
# HTTP Control server
- HTTP_CONTROL_SERVER_ADDRESS=:8000
- HTTP_CONTROL_SERVER_LOG=on
# Other
- PUBLICIP_PERIOD=12h
- VERSION_INFORMATION=on
- UPDATER_PERIOD=24h
- HEALTH_TARGET_ADDRESS=9.9.9.9:443
- PUBLICIP_API=ipinfo
- PUBLICIP_API_TOKEN=<REDACTED>
sysctls:
- net.ipv6.conf.all.disable_ipv6=1
restart: unless-stopped
sabnzbd:
<<: *base-service
image: ghcr.io/linuxserver/sabnzbd:latest
container_name: sabnzbd
volumes:
- /dockercfg/sabnzbd:/config
- /ssd/downloads/sabnzbd:/downloads
- /ssd/incomplete-downloads/sabnzbd:/incomplete-downloads
hydra2:
<<: *base-service
image: linuxserver/nzbhydra2:latest
container_name: hydra2
volumes:
- /dockercfg/hydra:/config
- /ssd/downloads/hydra:/downloads
deluge:
<<: *base-service
image: ghcr.io/linuxserver/deluge:latest
container_name: deluge
environment:
- DELUGE_LOGLEVEL=error # Optional
volumes:
- /dockercfg/deluge:/config
- /ssd/downloads/deluge:/downloads
networks:
default:
name: gluetun
I have the firewall on manual for docker maybe there is a problem. I allowed my IP address but that did not fix anything but should I maybe add a rewrite in my firewall?
This definitely doesn't look a Gluetun bug, more of a configuration issue on the host, so I'm converting this to a discussion. Feel free to continue the debugging conversation over there. If there is a fix for it that could be incorporated into Gluetun, then please later open a new issue and I'll look into it.
Is this urgent?
No
Host OS
Debian 12
CPU arch
x86_64
VPN service provider
ExpressVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on Jun 28, 2024
What's the problem 🤔
i cant access my services that are running behind the container. this is how i connect to my container: network_mode: container:gluetun gluetin itself is working and i can see its ip that is has. I want to access my services on port 8080 and 8082 but when i try connecting it just gives me: "site cant be reached" All my containers that are not in the gluetun network also can access the other services only things not on the computer cant acces them
Share your logs (at least 10 lines)
Share your configuration