"Invalid session" - Complete unraid beginner here, trying to figure this out.

[JamesSampsan]

Complete UnRaid beginner here. I've had my server set up for a few months now but can't get Mousehole working. I know I'm doing something obvious wrong, but I can't figure it out.

I'm using Binhex-qbittorrentvpn with wireguard set up. My VPN is through OVPN and I just throw the wg0.conf file into the wireguard folder in binhex-qbittorrentvpn.

binhex-qbittorrentvpn, Prowlarr, Radarr, Sonarr are all on a custom network.

When inputting my cookie, I get an "Invalid session - ASN mismatch" error, showing the HostIP as my public non-VPN IP. Qbittorrent's external IP at the bottom is the same that is shown in my "tracker errors - IP port" page. I used to be able to search for a specific item on Prowlarr after configuring that, and download it and it would send directly to binhex-qbittorrentvpn, but that doesn't seem to be working either.

Any help is appreciated,

Thanks

[ahatdude]

I think this is because your "Binhex-qbittorrentvpn" is accessing MaM via the OVPN IP and the mousehole container is accessing MaM via your normal IP, therefore there's a mismatch.

I'm also going through the same thing and I wonder if @t-mart would be open to making the docker container have an option of adding a wg0.conf file and routing the container through it to access MaM via the same IP as the qbittorrent container (whether binhex, LSIO, hotio etc.).

Cheers.

[t-mart]

@JamesSampsan, what @ahatdude is right -- Mousehole needs to be run on the same network as your VPN-ed bittorrent client. If you're seeing your home IP on mousehole, then you haven't done that correctly.

I do not use Unraid, so I cannot help you with that. However, @Mlitz recently wrote an Unraid guide. Maybe that will help you.

If you continue to run into issues, you'll get better community support from the forum post. There are more people there.

@ahatdude nah, that's too specialized. VPN support is the job of purpose-built VPN containers like the ones you mention.

mousehole as a sidecar onto other VPN containers definitely works. You just need to follow the rules of sidecar-ing

(Personally, I just migrated from a wireguard setup to a gluetun one and I highly recommend it now. Its config is dead simple and was a breeze to get working. See Gluetun + qBittorrent Docker Compose Example for the gist of it.)

[ahatdude]

Thanks for pointing me in the direction of the Unraid guide.

Since I've managed to fix it, maybe I can help @JamesSampsan and others, so I'll leave here how I fixed it via the UI, without the need to use docker-compose or gluetun - I just have the hotio qbittorrent docker with integrated VPN active (I guess binhex would be the same). One thing I did do, was configure it before since I'm not sure how to access the webui (I've tried adding the ports to the qbittorrent container, but nothing worked).

In the advanced view of the "Mousehole" container do the following:

1. Add "Extra Parameter": "--net=container:NAME_OF_CONTAINER_OF_YOUR_TORRENT_CLIENT"
2. Change "Network Type": "None"

The Mousehole container should now be directed via the qbittorrent container and using the same IP, therefore working properly - you can check the logs, they should look something like this:

$ NODE_ENV=production bun src/index.tsx
Mousehole v0.2.0 (c924097) running at http://localhost:5010/
Starting background update task...
No update needed, current state is ok
Next automatic update scheduled for: 2025-12-05T21:59:50.545+01:00[Europe/YOUR_TIME_ZONE]

[t-mart]

Add "Extra Parameter": "--net=container:NAME_OF_CONTAINER_OF_YOUR_TORRENT_CLIENT"

Yes, this will work. This is similar to writing service:NAME_OF_SERVICE_OF_YOUR_TORRENT_CLIENT as mentioned in the sidecar document.

However, there's a caveat: doing it this way, your torrent client container and mousehole can get out of sync.

Because mousehole has a dependency on the VPN network of the torrent client's container, if your restart the torrent client container, then mousehole will be left with a non-functioning orphaned network. The symptom you'll notice is that mousehole will fail at reaching out to MAM.

To fix it, you need to ensure that if you restart the torrent container, you then restart mousehole after. This allows mousehole to re-bind to the new container's network. (There is no easy way to make this happen automatically)

Many, many unraid users have run into this problem, especially if they are using data-backup solutions that routinely stop/start containers.

(I've only researched a bit about unraid, but I think this is one of the most unfortunate parts of it: it doesn't have good support for creating groups or stacks of containers. This is exactly what docker compose does, and you'll never run into this problem with it.)

[JamesSampsan]

Thanks everyone, adding the extra parameter worked. I am able to download torrent files on my desktop then just drag them into the qbittorrent webpage. My workaround had been making a session key for Prowlarr, so I could browse / download the torrent via Prowlarr, but it got to be a pain in the ass trying to grab the Freeleech stuff.

In regards to the syncing, I've set Mousehold to autostart after a a delay of 2 minutes, way more than enough time for things to get started and running, but I'll keep an eye out for those errors if they arise. I rarely reboot the server; about once a month to apply updates.

Also: for anyone who has issues in the future - I had to run mousehole normally so I could put in my sessionkey, otherwise after adding the extra parameter, it doesn't get assigned a container IP/Port so you can't use the WebUI to change it.

Thanks everyone!

[dpureco]

Hello from the future. Thanks to both of you for the instructions you've provided already, I just wanted to provide information on how to access Mousehole's WebUI for anyone that might find this thread. After doing the steps above (making the mousehole container with the network for your torrent client), you'll want to also add the Mousehole port (5010 by default unless you changed it) to your torrent client's container. For the binhex bittorrent container, I needed to add 5010 into the "VPN_INPUT_PORT". If you use a different container image, there's probably a similar port. I also had to create a new port mapping (I called it "Mousehole port" but the name is irrelevant) to your bittorrent container with a container port of 5010 and a host port of 5010 (both numbers need to match the WebUI port from the Mousehole container).

That's it, just start your torrent container and then your mousehole container and you should be able to get to the WebUI at your Unraid tower IP with port 5010.