Connecting Deluge to Sonarr via subdomain reverse proxy
reddit / selfhosted

----------------------------------------------------------------------
Independent_Fill_570 · 2023-12-11 00:58

I'm unable to connect my Download Client Deluge to Sonarr using the
hostname `deluge.mydomain.com` where `mydomain.com`is owned by me.

Screenshot: https://cdn.zappy.app/f279852410baed23d520e7b4a3579ead.png

I have confirmed it's reachable by curling using my domain

Screenshot: https://cdn.zappy.app/7231e7a574ba4998917cfd86898ec23a.png

So I'm left confused why I can manually ping this domain successfully
but Sonarr can't.

----------------------------------------------------------------------
thekrautboy · 2023-12-11 01:20

Are they both running on the same server? As containers on the same
host? Then simply place both into a shared Docker network and connect
them with their containernames as hostnames, no need to use external
domains.

Your problem is likely that your DNS name resolves to something that
the container cannot make sense of. But doing a curl from the outside
works.

----------------------------------------------------------------------
Independent_Fill_570 · 2023-12-11 01:34

The purpose for putting a reverse proxy on them is to get an SSL cert
so I stop getting the warning in my browser.  They are on the same
server/same host.  Just set to have a macvlan to get unique IPs.

From there I'm using Pihole to redirect to Nginx Reverse Proxy to give
them hostnames.  That way I never make an external leap to do a
hostname lookup.

I'm unsure how to not give them an external domain while still getting
https/SSL cert when visiting the web UIs.

----------------------------------------------------------------------
thekrautboy · 2023-12-11 01:45

You can still use the reverse proxy for external access. But there is
no point in connecting from deluge to sonarr through the proxy with
ssl, when they are running on the same machine. The macvlan is
probably ruining this and i dont see why you even use that for
dedicated IPs when you have a reverse proxy already.

----------------------------------------------------------------------
Independent_Fill_570 · 2023-12-11 01:47

Hm I wonder how I'd do this, then.  While keeping the UI access under
https/SSL cert.

I'd need to find a tutorial of this alternative method to learn more.

----------------------------------------------------------------------
thekrautboy · 2023-12-11 01:59

Very standard Docker setup with reverse proxy. You remove the macvlan,
you create a bridge Docker network for the proxy, then make all
containers that you want to proxy a member of it. You only map ports
of the proxy to the host, typically 80/443 tcp. And you connect from
the proxy to the containers using their containernames as hostnames
and their internal ports, the same when connecting from deluge to
sonarr and similar.

Plenty of guides about exactly this exist already.

----------------------------------------------------------------------
Independent_Fill_570 · 2023-12-11 02:23

Ah fair play.  Yeah I get it now.  I'll go down that path, thanks!