17 minutes ago, wgstarks said:

Qbittorrentvpn is running but I just get failed to connect

Did you also add it to your VPN_INPUT_PORTS list?

43 minutes ago, JonathanM said:

Did you also add it to your VPN_INPUT_PORTS list?

I don’t have that variable in my qbittorrentvpn docker template. Can you post a screenshot so I can add it?

Edited September 22, 20241 yr by wgstarks

1 hour ago, wgstarks said:

I don’t have that variable in my qbittorrentvpn docker template. Can you post a screenshot so I can add it?

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

See Q24

I added that variable and changed WEB_UI to localhost:3333 as dictated in the FAQ but still no dice. Also attaching supervisord.log since I'm seeing errors there.

 

qbittorrentvpn-

 

bitmagnet config-

 

 

supervisord.log

Update: It just started working. Maybe I just needed to wait a few more minutes. Still unable to add it to Prowlarr though.

 

 

Does Prowlarr also need to be running through the same VPN for this to work? Currently it's using Privoxy IIRC. Or maybe I'm just doing it wrong.😁

Also, is there anyway to only allow specified languages in the config file (or otherwise I guess)? I'm not seeing anything obvious but haven't checked all the docs.

32 minutes ago, wgstarks said:

Does Prowlarr also need to be running through the same VPN for this to work?

Yes, at least that's how I have mine configured.

9 hours ago, wgstarks said:

Does Prowlarr also need to be running through the same VPN for this to work?

Nope it doesn't need to be but it makes things simpler if it does, fyi this is what i have inside the vpn network (privoxyvpn):-

 

Prowlarr

Jackett

bitmagnet

flaresolverr

nicotine+

 

Then in a separate vpn tunnel is qbittorrentvpn, all other containers are on the standard host/bridge network, basically IMO you should only be putting applications inside the vpn network that either download files (torrent client) or download/interact with index sites.

 

But if you do want prowlarr to talk to bitmagnet then you will need to use the ip address of your server NOT 'localhost', you only use localhost if you are performing communication between two applications inside the same (vpn) network, so this is wrong:-
 

10 hours ago, wgstarks said:

I added that variable and changed WEB_UI to localhost:3333 as dictated in the FAQ

From the FAQ:- 

Quote

Please keep in mind that when defining connections from an application to another application in the same VPN container network that you will need to set the host to 'localhost' and NOT the LAN IP address,

This is not the case for you (as things currently stand).

One other comment, from your screenshot it looks like you are making things a little more complex than they need to be, prowlarr already has a pre-defined index site for bitmagnet. no need to define custom:-

1 hour ago, binhex said:

this is what i have inside the vpn network (privoxyvpn):-

 

Prowlarr

Jackett

bitmagnet

flaresolverr

nicotine+

So using qbittorrentvpn for the von network I can just add bitmagnet, Jackett, Prowlarr and flaresolver and leave Sonarr and Radarr with there current configuration connected to Privoxy? And this won’t effect there ability to connect to Jackett and Prowlarr?

 

FYI: I think they currently use localhost to connect to Privoxy.

Edited September 23, 20241 yr by wgstarks

29 minutes ago, wgstarks said:

leave Sonarr and Radarr with there current configuration connected to Privoxy?

proxy will add complexity to this and is no longer required, remember jackett/prowlarr now do the metadata downloading here not sonarr/radarr so no need to proxy.

1 hour ago, binhex said:

proxy will add complexity to this and is no longer required, remember jackett/prowlarr now do the metadata downloading here not sonarr/radarr so no need to proxy.

So this config will still work (with appropriate port numbers of course) for Sonarr/Radarr connected to local bridge network and Prowlarr/Jacket connected to VPN?

 

Edited September 23, 20241 yr by wgstarks

Just now, wgstarks said:

So this config will still work (with appropriate port numbers of course) for Sonarr/Radarr connected to local bridge network and Prowlarr/Jacket connected to VPN?

That's how mine is set up.

5 hours ago, wgstarks said:

So this config will still work (with appropriate port numbers of course) for Sonarr/Radarr connected to local bridge network and Prowlarr/Jacket connected to VPN?

it should do, yes, prowlarr pushes index configuration to radarr/sonarr, so if you can see the indexers appearing in radarr/sonarr then the chances are its configured correctly, hit the 'test' button to confirm but you should be good.

38 minutes ago, binhex said:

it should do, yes, prowlarr pushes index configuration to radarr/sonarr, so if you can see the indexers appearing in radarr/sonarr then the chances are its configured correctly, hit the 'test' button to confirm but you should be good.

If I test the Prowlarr indexers in radarr/sonarr the tests pass but Prowlarr is showing all apps unavailable. Doesn’t look like the sync function is working either.

 

Edited September 23, 20241 yr by wgstarks

2 minutes ago, wgstarks said:

If I test the Prowlarr indexers in radarr/sonarr the tests pass but Prowlarr is showing all apps unavailable. Doesn’t look like the sync function is working either.

If you go to settings, apps in prowlarr, do all your apps show up and test good?

9 minutes ago, wgstarks said:

but Prowlarr is showing all apps unavailable.

this is what my prowlarr app settings for sonarr look like, do yours look similar?:-



Also keep in mind you will need to permit prowlarr (inside the vpn) to talk to sonarr (outside the vpn), this is done by adding sonarr port to VPN_OUTPUT_PORTS list, like so:-

1 hour ago, binhex said:

Also keep in mind you will need to permit prowlarr (inside the vpn) to talk to sonarr (outside the vpn), this is done by adding sonarr port to VPN_OUTPUT_PORTS list, like so:-

This is probably the problem.

Added the variable VPN_OUTPUT_PORTS with the proper values and it’s working thanks to @binhex and @JonathanM for the help.👍👍👍

I'm seeing a few warnings in the log-

2024-09-23 21:26:28,201 DEBG 'start' stdout output:
WARN    dht_crawler     dhtcrawler/bootstrap.go:20      failed to resolve bootstrap node address: lookup dht.anacrolix.link on 1.1.1.1:53: no such host

2024-09-23 21:26:48,336 DEBG 'start' stdout output:
WARN    dht_crawler     dhtcrawler/bootstrap.go:20      failed to resolve bootstrap node address: lookup router.bittorrent.cloud on 1.1.1.1:53: no such host

 

Are these expected? The docker is working, just bothered by the warnings.

 

supervisord.log

 

15 minutes ago, wgstarks said:

Are these expected?

I believe so. Probably caused by clients advertising sources that are no longer online.

6 hours ago, wgstarks said:

Are these expected? The docker is working, just bothered by the warnings.

Ignore it, i see the same, i believe they are old DHT bootstrap endpoints that no longer exist, i would assume they will be removed in the next release.

i use appdata backup plugin to back up my containers appdata folders.

 

i am getting the following error when it runs:

 

can someone help me correct this?  thank you!

1 hour ago, knights_of_pine said:

i use appdata backup plugin to back up my containers appdata folders.

 

i am getting the following error when it runs:

 

can someone help me correct this?  thank you!

Pretty sure you just need to specify an exclusion for that path. It's out of the ordinary for the normal way of doing things, so it trips up the defaults in the backup plugin. It does not ever need to be backed up, it's simply a way for multiple separate binhex containers to share information.

so in the "excluded folders/files" i just type "binhex-shared"  no quotes?