search

ivan-pinatti / docker-torrent-box-with-vpn

Torrent / Usenet / NZB container stack with VPN (ProtonVPN) to be run by Docker Compose
MIT License
84 stars 14 forks source link

Web Apps not working on external ip #19

Closed RoxyBoxxy closed 1 year ago

RoxyBoxxy commented 1 year ago

Describe the scenario

Can not access apps or nginx https from external ip

What is your question?

Hi i can seem to access anything on a external network, i have installed this on a dedicated server and dont have access to desktop, i am using protonvpn wireguard and the protonvpn docker says its connected to wireguard but i dont get any pages

ivan-pinatti commented 1 year ago

Hello @RoxyBoxxy , could you provide more details about your architecture? Are you able to run it locally to validate that everything is working?

RoxyBoxxy commented 1 year ago

So i have just installed a vnc server on it and i cant even seem to access it via localhost

this is my proton log

[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[ERROR   ] Failed to connect to https://protonwire-api.vercel.app/v1/client/ip (timeout) ,
[ERROR   ] Failed to verify connection (1/5) ,
[WARNING ] Attempting to re-connect to nl-free-127.protonvpn.net ,
[WARNING ] Server info is stale - /tmp/protonwire.server.json ,
[INFO    ] Refresing server metadata (for nl-free-127.protonvpn.net) ,
[SUCCESS ] Successfully refreshed server metadata ,
[SUCCESS ] Server nl-free-127.protonvpn.net is online ,
[SUCCESS ] WIREGUARD_PRIVATE_KEY(KGJoA**********) is a valid key ,
[SUCCESS ] net.ipv4.conf.all.rp_filter is already set to 2 ,
[NOTICE  ] WireGuard interface 'protonwire0' already exists ,
[SUCCESS ] WireGuard interface already has address - 10.2.0.2/32 ,
[SUCCESS ] WireGuard interface MTU is already set to - 1480 ,
[SUCCESS ] Configured WireGuard private key ,
[WARNING ] WireGuard interface is configured wrong peer - zFkaDAaf8Xt6c1FY82sp5Ncw/pN+GB9asDtGDOWClzo=  185.107.56.76:51820 ,
[WARNING ] Removed peer - zFkaDAaf8Xt6c1FY82sp5Ncw/pN+GB9asDtGDOWClzo=  185.107.56.76:51820 ,
[INFO    ] WireGuard interface is configured with peer - zFkaDAaf8Xt6c1FY82sp5Ncw/pN+GB9asDtGDOWClzo=(185.107.56.75) ,
[SUCCESS ] WireGuard interface is already UP ,
[SUCCESS ] WireGuard interface fwmark is already set to - 0xca6d ,
[NOTICE  ] Validating Killswitch routes (IPv4) ,
[SUCCESS ] Routes are algrady configured (IPv4) ,
[SUCCESS ] Killswitch is algrady configured (IPv4) ,
[SUCCESS ] Routing policy rule is already configured (IPv4) ,
[SUCCESS ] DNS is already set to 10.2.0.1 in /etc/resolv.conf ,
[SUCCESS ] Successfully configured DNS (resolvconf) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[NOTICE  ] Successfully reconnected to nl-free-127.protonvpn.net ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[ERROR   ] Failed to connect to https://protonwire-api.vercel.app/v1/client/ip (timeout) ,
[ERROR   ] Failed to verify connection (2/5) ,
[WARNING ] Attempting to re-connect to nl-free-127.protonvpn.net ,
[SUCCESS ] Server nl-free-127.protonvpn.net is online ,
[SUCCESS ] WIREGUARD_PRIVATE_KEY(KGJoA**********) is a valid key ,
[SUCCESS ] net.ipv4.conf.all.rp_filter is already set to 2 ,
[NOTICE  ] WireGuard interface 'protonwire0' already exists ,
[SUCCESS ] WireGuard interface already has address - 10.2.0.2/32 ,
[SUCCESS ] WireGuard interface MTU is already set to - 1480 ,
[SUCCESS ] Configured WireGuard private key ,
[SUCCESS ] WireGuard interface already has peer - zFkaDAaf8Xt6c1FY82sp5Ncw/pN+GB9asDtGDOWClzo=(185.107.56.75:51820) ,
[SUCCESS ] WireGuard interface is already UP ,
[SUCCESS ] WireGuard interface fwmark is already set to - 0xca6d ,
[NOTICE  ] Validating Killswitch routes (IPv4) ,
[SUCCESS ] Routes are algrady configured (IPv4) ,
[SUCCESS ] Killswitch is algrady configured (IPv4) ,
[SUCCESS ] Routing policy rule is already configured (IPv4) ,
[SUCCESS ] DNS is already set to 10.2.0.1 in /etc/resolv.conf ,
[SUCCESS ] Successfully configured DNS (resolvconf) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[NOTICE  ] Successfully reconnected to nl-free-127.protonvpn.net ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83) ,
[SUCCESS ] Connected to nl-free-127.protonvpn.net (via 185.107.56.83)
ivan-pinatti commented 1 year ago

Hi @RoxyBoxxy,

If you can run it locally before trying to make it work on an external server it would be easier to help you debug the issue you are facing. Unfortunately, without knowing your architecture, what you are trying to achieve, etc... I can't help that much.

The logs aren't too helpful as it only shows that the ProtonVPN container is connected.

RoxyBoxxy commented 1 year ago

So i am trying to run this on a server to be a seedbox how ever the datacenter does not allow torrent apps or seeding, i have accessed it on localhost on the server how ever it just keeps saying "The Connection was reset", i accessed localhost with nginx using https and the only page i got was qbittorrent witch asked for a login then said unauthorised. my end goal is to get DOCKER > Public ip + port, so i can access it from my home network using my browser

ivan-pinatti commented 1 year ago

The problem is more on your network architecture / configuration then the container stack itself, you will have to make adjustments on your host machine and firewall rules to achieve that.

Are there any problems in the stack itself that you would like to report?

stale[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.