search

tenseiken / docker-qbittorrent-wireguard

Docker container which runs qBittorrent-nox (headless) client while connecting to WireGuard.
GNU General Public License v3.0
8 stars 3 forks source link

misconfig in iptables.sh? #3

Closed Antediluvia-stack closed 3 days ago

Antediluvia-stack commented 1 month ago

When running docker compose up, the following error is printed to the console:

qbittorrent-wireguard  | /etc/qbittorrent/iptables.sh: line 87: /etc/iproute2/rt_tables: No such file or directory
qbittorrent-wireguard  | /etc/qbittorrent/iptables.sh: line 88: /etc/iproute2/rt_tables: No such file or directory
qbittorrent-wireguard  | Error: argument "webui" is wrong: invalid table ID
qbittorrent-wireguard  |
qbittorrent-wireguard  | Error: argument "webui" is wrong: "table" value is invalid

Once the container is running, the authentication page of the Web gui is accesible, but once credentials are submitted the following page fails to load.

tenseiken commented 1 month ago

Let me preface this by saying that almost all of that particular script came over from the repo I forked from, and I haven't really dug into how it all works.

Looking at the logic in that script, lines 87 and 88 are only run if lsmod | grep iptable_mangle returns zero. In my container, it looks like that doesn't happen but it must be for you, which makes me think there's something fundamentally different between your container and mine.

The Docker-Compose.yml file I include in this repo is very similar to what I run in my own environment. Did you base your compose file on that one or make your own?

Is your host system running ARM architecture (ex: Raspberry Pi) or AMD64 (ex: Intel, AMD)?

Does the file /etc/iproute2/rt_tables actually exist within your container? The error message indicates that it doesn't. Presumably it would be placed by iproute2, but I'm not sure about that off-hand.

Anyway, my suggestion at this point (without having the answers to the above questions) would be to comment out the if statement from line 83 to line 91 in /etc/qbittorrent/iptables.sh within the container and then restart the container. See if it behaves then.

tenseiken commented 3 days ago

Resolved by #6