Closed zilexa closed 4 years ago
Never mind. Your solution works. What went wrong: I ran my docker-compose.yml -up again with a slightly different CIDR, after that, even if I changed it back to the correct CIDR, I could not access any webui that ran via the VPN network. Even after deleting the container. I ended up deleting everything: containers, images, the folders in /docker folder and ran my docker-compose.yml. It works now.
Unfortunately, there does seem to be something wrong here. After the container has been created for the first time via compose, everything works. I can access the webuis via the ports that I have opened via the vpn config in my compose file.
If I want to open another port, via docker-compose.yml, I change my yml file and run it. After the docker_vpn_1 is recreated, and the container is running (checked with Portainer) none of the ports seem to work.
As I am still learning, I don't know how to debug this one any further. My docker apps work fine, but not if I run them via the nordvpn-proxy. I have defined the ports required for them (moving them in my docker-compose.yml to nordvpn-proxy).
Here is my docker-compose.yml: https://github.com/zilexa/Mediaserver/blob/master/docker-compose.yml
By commenting out the ports under nordvpn-proxy and adding them back in each docker configuration, I can access the apps again.
Is there any way (via Portainer, terminal) to test inside the nordvpn-proxy what is going wrong?
Also, I don't use Privoxy yet but when I access localhost:privoxy I get "Invalid header received from client."
edit, I got my network CIDR mask via:
meaning it should be: 192.168.88.0/24