SOLVED Unable to connect qbittorrent to sonarr/radarr using Kubernetes internal dnsname

SirNomad49

Cadet
Joined
Jul 10, 2021
Messages
9
Hello,

for some reason I am not able to setup qBittorrent with sonarr or radarr through the internal dns name.

1645911853536.png


I am using OpenVPN in the qBittorrent Application:

from the ovpn pod I am able to ping the name: qbit-qbittorrent.ix-qbit.svc.cluster.local
1645912085552.png


It is also not working through the internal ip:

1645912222481.png


My Application is named qbit:
1645911890499.png


I was following the guide from @truecharts

In the other pods I do not have ping so I cant try to reach them through the Kubernetes network

Setting up Prowlarr with Sonarr & Radarr is working without problems:

1645911823878.png





But when I am using it through the NAS IP with the exposed port it is working:
1645912302203.png


Did anyone encounter this error?
 

SirNomad49

Cadet
Joined
Jul 10, 2021
Messages
9
Hello,

for some reason I am not able to setup qBittorrent with sonarr or radarr through the internal dns name.

View attachment 53540

I am using OpenVPN in the qBittorrent Application:

from the ovpn pod I am able to ping the name: qbit-qbittorrent.ix-qbit.svc.cluster.local View attachment 53542

It is also not working through the internal ip:

View attachment 53543

My Application is named qbit:
View attachment 53541

I was following the guide from @truecharts

In the other pods I do not have ping so I cant try to reach them through the Kubernetes network

Setting up Prowlarr with Sonarr & Radarr is working without problems:

View attachment 53539




But when I am using it through the NAS IP with the exposed port it is working:
View attachment 53544

Did anyone encounter this error?
The big problem was my thinking.

I thought the port internally in the kubernetes network should be 8080 as configured in the qbittorrent application but it is using the same port as in the existing configuration which is 10095 in my case.

1645913143864.png
 
Top