Closed aneurinprice closed 1 year ago
This doesnt seem to be a basic network issue as the Gluten container works just fine for me.
I have the same issue
I have the same issue
I used the Gluetun container with the below config.
version: "3"
services:
vpn:
image: qmcgaw/gluetun
cap_add:
- NET_ADMIN
environment:
- VPN_SERVICE_PROVIDER=nordvpn
- OPENVPN_USER=<redacted>
- OPENVPN_PASSWORD=<redacted>
- REGION=United Kingdom
ports:
- 8080:8080
I have the same issue
I used the Gluetun container with the below config.
version: "3" services: vpn: image: qmcgaw/gluetun cap_add: - NET_ADMIN environment: - VPN_SERVICE_PROVIDER=nordvpn - OPENVPN_USER=<redacted> - OPENVPN_PASSWORD=<redacted> - REGION=United Kingdom ports: - 8080:8080
Thanks! Gluetun works like a charm!
Same issue here, if i /bin/bash on the container it self and i type curl ifconfig.me it gives me the vpn IP But whenever i connect any container that container will not have an internet connection.
Using a synology nas with docker.
I have the same issue as @crryp. the container says it's connected, but other containers (bash-test in this case) can't access the internet. I'm pinging 8.8.8.8 with no results. and google.com says bad address
Tried TECHNOLOGY as NordLynx/OpenVPN. Tried with and without DNS=... Using ports 8090:8080 as 8080:.. is already taken, although I'm not sure I need this as I'm not interested in Ingress traffic (at least for now)
Weird thing is on another machine it doesn't even connect (it tries to connect to several vpn servers and it fails, with the same docker compose file)
services:
bdapi-vpn:
image: ghcr.io/bubuntux/nordvpn
container_name: bdapi-vpn
cap_add:
- NET_ADMIN # Required
- NET_RAW # Required
environment: # Review https://github.com/bubuntux/nordvpn#environment-variables
- TOKEN=<redacted> # Required
# - CONNECT=United_States
- CONNECT=Spain
# - TECHNOLOGY=NordLynx
- TECHNOLOGY=OpenVPN
- NETWORK=192.168.1.0/24 # So it can be accessed within the local network
- DNS=1.1.1.1,8.8.8.8
ports:
- 8090:8080
sysctls:
- net.ipv6.conf.all.disable_ipv6=1 # Recomended if using ipv4 only
bash-test:
image: bash
network_mode: service:bdapi-vpn
depends_on:
- bdapi-vpn
command: sleep 9999999
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.
I am still having this issue...!
me too!
it constantly disconnects too, making my app unusable. I have to restart the containers every 2-3 hours. is that the expected behavior? I want to run a semi-permanent server that uses nordvpn. no luck so far
use gluetun instead, works very reliably
use gluetun instead, works very reliably
actually that's what I started using a while ago, because I couldn't get other solutions to work, but the issue remains. it keeps disconnecting while I was expecting 5 connections to always be active
Have you guys checked the loggin on the container startup? It kinda suggests switching over to the new project.
I am pretty sure the author has stopped supporting this project. Unless you have a good reason to use the old NordVPN protocol (like having AES-NI cpu capabilities) I would suggest switching to the new project that uses nordlynx and wireguard: https://github.com/bubuntux/nordlynx/ Wireguard uses cha-cha so can be run faster on even the more simpler CPU's like raspberry pi/router/NAS etc. Hopefully this helps you all guys!
Describe the bug When deploying the VPN container, the container connects to NordVPN successfully, but has no internet access.
To Reproduce using docker-compose docker-compose.yml if used (hide credentials)
Expected behavior I would expect the containers in this compose to have some form of internet access.
Logs VPN Container:
Additional context This is running on a Proxmox VM with a flat /16.
Other containers on the host have internet access with no problems.
Running the above stack on my mac also does not work.
Any help would be appreciated on this one as I don't quite know what is going on.