[Solved] Issue with qBittorrent and Gluetun After YAMS Installation

[vonhardy]

Hi everyone,

I recently went through what I believe is a pretty standard installation of YAMS on a Debian 12 VM. I followed the steps outlined in the YAMS Installation Guide, including setting up a VPN using Surfshark.

At the end of the setup, I was presented with the expected service URLs and no errors. Next, I moved on to configuring qBittorrent. The first step was to run yams check-vpn.

However, I encountered the following error:

Code: Select all

Getting your IP...
Your IP: xxx.xxx.xxx.xxx
Your local IP country is Canada

Getting your qBittorrent IP...
Failed to get qBittorrent IP from any endpoint

I then tried accessing qBittorrent via 192.168.x.x:8081, but nothing loaded. Here’s what I’ve done to troubleshoot so far:

Checked qBittorrent Logs
Ran docker logs qbittorrent and found no error messages. The log ends with:

Code: Select all

Connection to localhost (::1) 8081 port [tcp/tproxy] succeeded!

Checked Docker Port Assignments
Ran docker ps and noticed that all containers had ports assigned correctly, except for gluetun and qbittorrent, which showed empty “PORTS” fields.

Ran docker logs gluetun and found the following error message:

Code: Select all

2025-01-08T12:53:44Z INFO [routing] default route found: interface eth0, gateway 172.18.0.1, assigned IP 172.18.0.11 and family v4
2025-01-08T12:53:44Z INFO [routing] local ethernet link found: eth0
2025-01-08T12:53:44Z INFO [routing] local ipnet found: 172.18.0.0/16
2025-01-08T12:53:44Z INFO [firewall] enabling...
2025-01-08T12:53:44Z INFO [firewall] enabled successfully
2025-01-08T12:53:45Z INFO [storage] merging by most recent 20776 hardcoded servers and 20776 servers read from /gluetun/servers.json
2025-01-08T12:53:45Z ERROR VPN settings: provider settings: server selection: for VPN service provider surfshark: port forwarding only filter is not supported

Observations/Questions
It seems that Gluetun is encountering issues with Surfshark’s port forwarding configuration, which may be causing qBittorrent to fail to bind its WebUI (8081) to the network.

According to the error, I'm guessing it could have something to do with one of these lines in docker-compose.yaml:
environment, but I don't see any mention of tweaking this in the VPN Guide, even though I am using one of the recommended VPNs, so I'm unsure how to proceed safely.

Code: Select all

      - VPN_SERVICE_PROVIDER=${VPN_SERVICE}
      - VPN_TYPE=openvpn
      - OPENVPN_USER=${VPN_USER}
      - OPENVPN_PASSWORD=${VPN_PASSWORD}
      - OPENVPN_CIPHERS=AES-256-GCM
      - PORT_FORWARD_ONLY=on
      - VPN_PORT_FORWARDING=on

Is the error in Gluetun related to Surfshark’s VPN setup? If so, how can I resolve this? Should I modify Gluetun or qBittorrent configurations to get the WebUI working? I feel like I'm close to finding the issue, but I am unsure where to go next.

Any help appreciated!
Thank you

[rogs]

Hey @vonhardy!

Thank you for such a detailed question!

This is a known bug in YAMS, you can see the ticket here: https://gitlab.com/rogs/yams/-/issues/42

To fix it:

• Stop YAMS
• Remove this from your docker-compose file since SurfShark doesn't allow port forwarding:

  Code: Select all

        - PORT_FORWARD_ONLY=on
        - VPN_PORT_FORWARDING=on

• Restart YAMS

That should work! If it doesn't please let us know here!

Cheers!

Roger.

[vonhardy]

Ah! Missed that ticket... Now I can access qBittorrent!

However, when I run yams check-vpn, I get:

Code: Select all

Getting your qBittorrent IP...
Failed to get qBittorrent IP from any endpoint

Any idea where to go from there?

Thanks

[rogs]

That's weird... Is qbittorrent working and downloading? It might be an issue with surfshark blocking the IP checkers. Make sure gluetun works, check the logs as well.

Cheers!

Roger.

[vonhardy]

OK, so instead of doing yams restart, I just rebooted my VM completely and now it works!

Cheers!

[rogs]

Great! I'll mark it as solved. Thank you!