Connect overseerr to radarr running under gluetun
reddit / selfhosted

----------------------------------------------------------------------
drbasar · 2023-11-30 14:00

I have a stack of containers with qBitTorrent, radarr and others
running under a VPN with gluetun.

Now, I want to connect another container (not in the same stack) with
overseerr. I already put it in the same network as the gluetun
container but I still cannot connect overseerr to radarr.

I had this set up in the past and I remember that I followed a gluetun
guide to set up the networks, but I can't find it now. I remember that
it was something along the lines of what I am trying to do.

Is this the correct way? What am I missing? In overseerr, I just put
my IP address and the radarr port, but I already tried with localhost
too. With localhost the connection test fails instantly, with my IP it
takes a long time but eventually fails too.

----------------------------------------------------------------------
typkrft · 2023-11-30 16:46

I just put any container that needs gluetun in the same stack. I know
that's not the answer you want, but I'm not sure why you wouldn't.
Overseer is pretty much directly related to the programs that are
already in your stack.

----------------------------------------------------------------------
drbasar · 2023-11-30 19:59

That would be ideal and I tried that before but then I could not find
Plex from Overseerr which was running under Gluetun. At the time, I
searched for solutions but in the end, they all seemed much more
complex than just putting Overseerr out of the stack and I couldn't
get it to work that way.

----------------------------------------------------------------------
typkrft · 2023-11-30 20:38

Here's my configs and some examples.

https://pastebin.com/cJxtYZPv

----------------------------------------------------------------------
HexTrace · 2023-12-01 20:13

Add in the following variable to the GlueTun compose file (or the
equivalent for the command line to run it).

    environment:
      - FIREWALL_OUTBOUND_SUBNETS=10.0.0.0/16

And replace the 10.0.0.0/16 with the IP or subnet for the local
machine. This will allow the GlueTun network to accept connections
from that IP or subnet.

In my case I have Overseerr running on a VPS and a wireguard tunnel
back to my server at home, so I have both my wireguard network and
local network listed (example IPs, not actually the ones I use):

    environment:
      - FIREWALL_OUTBOUND_SUBNETS=10.0.0.0/24,192.168.0.0/24

This allows the inbound connection from Overseerr across port 5055 on
the wireguard network to reach anything running on the GlueTun stack,
as well as any other containers on the machine running GlueTun but
spun up under a different compose file or stack.