Doesnt work when connected to NordVPN, which ports need whitelisted?

[Tiypoh]

I've completed the following steps:

• Read Loop Warning on Readme
• Done the troubleshooting from Readme
• Checked if such issue already exists

OS

Docker - Debian

Platform and model

Home Server

Architecture

x86-64

Website

No response

Describe the bug

Works as soon as I disconnect from Nord, but while connected the prowlarr test ping that doesnt even need to bypass captcha takes 53 seconds, and so does the test on ext.to, almost exactly 53 seconds each time, responds with a 200 POST code but Prowlarr says it hasn't bypassed captcha.

INFO:     From: 172.17.0.1 at 2025-02-27 21:37:19: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 53.00s
INFO:     172.17.0.1:34376 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-27 21:40:42: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 53.03s
INFO:     172.17.0.1:58462 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-27 21:41:40: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 54.14s
INFO:     172.17.0.1:55940 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-28 01:22:27: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 53.00s
INFO:     172.17.0.1:51780 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-28 04:55:20: https://ext.to/browse/?sort=seed&order=desc&age=0&with_adult=1
INFO:     Done https://ext.to/browse/?sort=seed&order=desc&age=0&with_adult=1 in 53.00s
INFO:     172.17.0.1:53524 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-28 07:23:29: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 106.07s
INFO:     172.17.0.1:38140 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-28 13:25:30: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 53.00s
INFO:     172.17.0.1:52654 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-28 17:49:01: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 53.03s
INFO:     172.17.0.1:54660 - "POST /v1 HTTP/1.1" 200 OK
INFO:     From: 172.17.0.1 at 2025-02-28 19:26:31: https://prowlarr.servarr.com/v1/ping
INFO:     Done https://prowlarr.servarr.com/v1/ping in 53.04s
INFO:     172.17.0.1:41764 - "POST /v1 HTTP/1.1" 200 OK

I already whitelisted port 8191 and 8192 just in case, but i see that the info ip often has a random port attached to it (i.e. 41764, 54660, 52654), im wondering if perhaps nordvpn is messing with the data on these ports and so if that port was to remain constant and I could whitelist it, perhaps that would work? Either way I need Nord active since this software runs on the same server downloading my torrents.

Additional context

No response

[ThePhaseless]

FastAPI ports info, basically this is the port of the client, not server, it is dynamically allocated. That's normal behavior even without any VPNs

[ThePhaseless]

Also, I can see that you're using an old version. Please update

[ThePhaseless]

If the issue persists, disable torrent client and vpn and try using /docs to bypass the website and see if that works

[Tiypoh]

@ThePhaseless My bad, I forgot I tried going back a version before I realized it was Nord messing it up, just tested it again on the latest and it is indeed still doing the same thing. I understand the dynamic port is normal behavior, I was just curious if it could be switched to static and whitelisted in nord if that might fix my problem. I'm not sure what you mean by using docs to bypass the website, but disabling my vpn does work, itll go right back to verifying within 3-4 seconds and work flawlessly, like I said before, but of course I cant use my server without it.

[ThePhaseless]

By docs I mean go to the URL:
byparrip:8191/docs with your browser and try using webui and try the request, but you've already confirmed it does work and it's a VPN issue

[Tiypoh]

Okay so what do I try next?

[Tiypoh]

I should also mention ive tried both tcp and udp protocols on nord, as well as switching between nordlynx and openvpn, with of course no success

[ThePhaseless]

My guess is that the IP that Nord is giving you has been flagged as VPN IP so cloud flare could block it everytime. Try if you could somehow use your torrent client with VPN but not byparr