19 hours ago, strike said:

First, change your vpn password (and user if you can), as you forgot to redact them from the log. Second, set STRICT_PORT_FORWARD to no. And thrid, see Q17: https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Thank you, ultimately what fixed it was replacing an outdated config file. I appreciate the help!

17 hours ago, strike said:

But why are you messing with input/output ports then? That should only be used if the containers are behind the delugevpn container.

Behind Deluge I have Prowlarr and Flaresolvarr which is also unable to connect (which is what the ports are used for) but also if the VPN is enabled would I not need to have the ports for input set for the external containers to access Deluge? or is Deluge not considered behind the VPN?

17 hours ago, strike said:

Have you enabled host access to custom networks in settings-Docker?

Yes this is enabled

17 hours ago, strike said:

Do you have proxy enabled in sonarr/radarr?

No I have not as I didnt know this was considered a proxy and didnt know the settings how to apply that as a proxy? I normally would think of something like nginx as a proxy but this I considered as just like I would connect to the WebUI using the IP it would be the same concept. Can you advise how the proxy settings should be setup when communicating with an app behind the VPN? I assumed if all the ports and containers were mapped they would flow the IP across (LIke when I access the WebUI for Prowlerr it works fine no issues, but asking to verify a site then fails.