Radarr mapping help

[Bwithnewcast]

Hey,

 

So i have been fumbling around trying to make my own home server stack and i have gotten to the point where i set up the gluetun vpn, before i ran it without and i cant seem to find a good way to map radarr inside prowlarr, i have found out i can use

Prowlarr server URL as Radarr sees it : http://gluetun:9696 and that is how radarr sees prowlar because they are on the same network called proxy

URL used to connect to Radarr server, including http(s)://, port, and urlbase if required and here i used radarr.domain.com but isnt there a more elegant way to do this where it does not have to reach out to the public just to comunicate? Here is also the link to the github repo with my stack: https://github.com/Bwithnewcast/ultimate-jellyfin-stack/tree/main

 

All help apreciated

[BoomerDutch]

Yes you can avoid domain by using internal ip addresses which you have three options is by setting static ip addresses for each application in docker then you're connecting in core but some may not work then you can use outside the docker which is the host. That means lan IP address like 192.168.x.x.

 

You can also attempt to use hostname for each application and try connect through hostname instead.

 

As long you understand networking then it should be easy.

 

I've used both options because most applications is connected through docker network except couple docker applications couldn't connect for some reason so I've used host ip address instead.

 

And yes you can still use domain to connect it's just for docker application it sees lan and internet technically mini computer.

 

 

Technically for some people sees domain as url but also ip address is domain as well hence sometimes confusing.

 

Because it's simply alias for ip address.

 

 

-edit i forgot to add.

For core docker network ports you should know the default ports in those default images like the application uses 443 as internal port and external port is 81 for example like 443:81 so 81 is lan ip address and 443 is internal ip address.

 

So yeah it requires thinking how you're connect each other to which port and which address.

[Bwithnewcast]

9 hours ago, BoomerDutch said:

Yes you can avoid domain by using internal ip addresses which you have three options is by setting static ip addresses for each application in docker then you're connecting in core but some may not work then you can use outside the docker which is the host. That means lan IP address like 192.168.x.x.

 

You can also attempt to use hostname for each application and try connect through hostname instead.

 

As long you understand networking then it should be easy.

 

I've used both options because most applications is connected through docker network except couple docker applications couldn't connect for some reason so I've used host ip address instead.

 

And yes you can still use domain to connect it's just for docker application it sees lan and internet technically mini computer.

 

 

Technically for some people sees domain as url but also ip address is domain as well hence sometimes confusing.

 

Because it's simply alias for ip address.

 

 

-edit i forgot to add.

For core docker network ports you should know the default ports in those default images like the application uses 443 as internal port and external port is 81 for example like 443:81 so 81 is lan ip address and 443 is internal ip address.

 

So yeah it requires thinking how you're connect each other to which port and which address.

I get to map prowlarr inside npm with gluetun:port, and also radarr at radarr:port etc, but i cant map radar inside prowlarr to radarr:port if that makes any sense. Radarr sees prowlar by mapping it to gluetun:port but not the other way

[BoomerDutch]

No can't seems figure out what you actually mean.

 

So far here are possible connections that i know of.

for example addresses you can connect to.

 

Docker internal way: 172.16.1.5:3444

Host internal way: 192.168.1.7:81

Vpn internal way: 10.10.10.15:81

Public address: xxx.xxx.xxx.xxx:81

 

Hope this helps.

[Bwithnewcast]

12 minutes ago, BoomerDutch said:

No can't seems figure out what you actually mean.

 

So far here are possible connections that i know of.

for example addresses you can connect to.

 

Docker internal way: 172.16.1.5:3444

Host internal way: 192.168.1.7:81

Vpn internal way: 10.10.10.15:81

Public address: xxx.xxx.xxx.xxx:81

 

Hope this helps.

Thinking of inside prowlarr by what url prowlarr sees radarr as, as of now i am using radarr.domain.com but i would rat er be using dockers internal dns

[BoomerDutch]

5 minutes ago, Bwithnewcast said:

Thinking of inside prowlarr by what url prowlarr sees radarr as, as of now i am using radarr.domain.com but i would rat er be using dockers internal dns

Then i would suggest to add hostnames to the containers and connect that way.

Like lttstore.lan for example or lttstore.local could work in some.

 

If it doesn't work then try just name and see if it works, unfortunately I'm not confident about using hostnames since it never worked for me so I've used ip addresses instead.

 

Lastly you could use ip address as domain though. Like https://192.168.1.15:81 so...

[Bwithnewcast]

14 minutes ago, BoomerDutch said:

Then i would suggest to add hostnames to the containers and connect that way.

Like lttstore.lan for example or lttstore.local could work in some.

 

If it doesn't work then try just name and see if it works, unfortunately I'm not confident about using hostnames since it never worked for me so I've used ip addresses instead.

 

Lastly you could use ip address as domain though. Like https://192.168.1.15:81 so...

I use hostnames but prowlarr cant reach radarr by internal hostname

 

[BoomerDutch]

43 minutes ago, Bwithnewcast said:

I use hostnames but prowlarr cant reach radarr by internal hostname

 

Then they configured that image that way for some reason, you could use your router dns settings and set domain to that ip address and use that domain you set on the radarr but not quite sure it would take that dns server or it's using docker dns instead maybe you can configure it.

 

Or another simple hack is by binding /etc/hosts and configure it instead.

 

Hope it helps.

[Bwithnewcast]

2 hours ago, BoomerDutch said:

Then they configured that image that way for some reason, you could use your router dns settings and set domain to that ip address and use that domain you set on the radarr but not quite sure it would take that dns server or it's using docker dns instead maybe you can configure it.

 

Or another simple hack is by binding /etc/hosts and configure it instead.

 

Hope it helps.

I have the solution i my head now, but thanks for the sugestions going to add prowlarr to the starr network that is only internat so they can comunicate with each other, silly me