misioslav/expressvpn

expressvpn's Issues

Mikrotik Assistance

Hi there,

I'm trying to run this on a mikrotik instance and having some real trouble getting my activation code into the docker. It won't let me enter it at the point of 'expressvpn activate' and I have tried all sorts of environment variables to get the code in that way (CODE, ACTIVATION_CODE, ENV CODE) but no luck. I'm new to containers in general so I'm sure this is my fault. Any chance you can assist ?

Connect host LAN device to published port?

Is there a way to configure the container such that you can connect a LAN device on the host directly to a published port?

Similar to how Gluetun handles it via HTTP proxy: https://github.com/qdm12/gluetun/wiki/Connect-a-LAN-device-to-gluetun

Gluetun isn't playing very nice with ExpressVPN so I'd like to try this tool out, thanks.

latest version restart loop

Not sure what is wrong as there are no errors or anything, but I updated to latest version and it starts just fine logs look normal and then it restarts. Infinitely.

I go back to 3.68.0.2 and everything works fine.

"please activate your account"

root@3da5b1035cc0:/# expressvpn connect
Connecting to Smart Location...
Connecting to Japan - Shibuya...
Unable to connect to Japan - Shibuya

• Check your internet connection or try a different location.
• Internet traffic is blocked to protect your privacy.
• To retry the connection, type 'expressvpn connect'
• To disconnect from the VPN and unblock internet traffic, type 'expressvpn disconnect'
  root@3da5b1035cc0:/# expressvpn diagnostics
  Client Version: 0.0.1default
  Client Shared Version: v23.21.0
  OS Name: linux
  OS Version: Debian GNU/Linux 11
  Internal diagnostics data:
  D01: 448, OK
  D02: 447, OK
  D03: 438
  D04: 438, OK
  D05: 438, OK
  D06: 438
  D07: 438, OK
  D08: 438, OK
  D09: 86707912
  D10: 438, OK
  D11: 438, OK
  D12: N, N
  D13: www.2spb2qq8pnqmv.net/api
  D14: Japan - Shibuya
  D15: auto
  D17: 438, OK
  D18: 0
  Network Lock: enabled, allow access to local devices
  DNS leak protection: enabled
  IPv6 leak protection: enabled
  Selected location: Japan - Shibuya (Smart Location)

==============================================

Connecting to Japan - Shibuya, ip: 24.123.193.169, protocol: lightway_udp

Client Version: 0.0.1default
Client Shared Version: v23.21.0
OS Name: linux
OS Version: Debian GNU/Linux 11
Internal diagnostics data:
D01: 432, OK
D02: 431, OK
D03: 422
D04: 422, OK
D05: 422, OK
D06: 422
D07: 422, OK
D08: 422, OK
D09: 86707896
D10: 422, OK
D11: 422, OK
D12: N, N
D13: www.2spb2qq8pnqmv.net/api
D14: Japan - Shibuya
D15: auto
D17: 422, OK
D18: 0

can't connect please help me

ping

Can you add ping to the base image? I prefer to use something like this for health:

healthcheck:
  test: "ping -c 1 -I tun0 www.google.com || exit 1"
  interval: 30s
  timeout: 10s
  retries: 3

I can install ping easily enough, but it starts to be a pain doing it every time the container is re-created

docker compose `command` never executes

Following the example in polkaned/expressvpn, i added

command: /bin/bash -c "cp /etc/resolv.conf /share/resolv.conf"

to my compose.yaml under the expressvpn service.

But it looks like this never executes. I think this line might be preventing it

expressvpn/files/start.sh

Line 47 in 0ee0822

tail -f /var/log/temp.log

Expressvpn Activation code not working.

    # Deluge - Download Client
    deluge:
        image: ghcr.io/linuxserver/deluge
        container_name: deluge
        # hostname: deluge
        environment:
            - PUID=${PGID}
            - PGID=${PUID}
            - TZ=${TZ}
            - DELUGE_LOGLEVEL=error #optional
        volumes:
            - ${USERDIR}/docker/deluge:/config
            - ${USERDIR}/Downloads/completed:/downloads
        # ports:
        #     - 8112:8112
        #     - 6881:6881
        #     - 6881:6881/udp
        restart: unless-stopped
        network_mode: service:expressvpn
        depends_on:
        - expressvpn

    expressvpn:
        image: misioslav/expressvpn:latest
        container_name: expressvpn
        restart: unless-stopped
        ports: # ports from which container that uses expressvpn connection will be available in local network
        - 80:80 # example
        - 8112:8112
        - 6881:6881
        - 6881:6881/udp
        environment:
        - CODE=${EVPNACTCODE} # Activation Code from ExpressVPN https://www.expressvpn.com/support/troubleshooting/find-activation-code/
        - SERVER=usda # By default container will connect to smart location, list of available locations you can find below
        # - DDNS=yourDDNSdomain # optional
        # - IP=yourStaticIP # optional - won't work if DDNS is setup
        # - BEAERER=ipinfo_access_token # optional can be taken from ipinfo.io
        # - HEALTHCHECK=HEALTCHECKS.IO_ID # optional can be taken from healthchecks.io
        # - NETWORK=off/on #optional and set to on by default
        cap_add:
        - NET_ADMIN
        devices:
        - /dev/net/tun
        stdin_open: true
        tty: true
        command: /bin/bash
        privileged: true

Hello, I'm using the following configuration in my docker-compose.yml, however, I keep getting this error in the logs of the expressvpn container.

This activation code has either expired or is incorrect. Please log in to our website to get your correct activation code and 
try again.

If you have any questions, please contact us.
send: spawn id exp4 not open
    while executing
"send "n\r""
    (file "/tmp/expressvpnActivate.sh" line 6)
Please activate your account.
Please activate your account.
Please activate your account.
Please activate your account.

I've doubled and triple checked that the activation code is activated and working. Do I need to use a different code? I see there are a number of device options.

Latest images not allowing dns

Ever since the latest release no dns traffic works in connected containers.
I get the following:

nslookup google.com
nslookup: write to '1.1.1.1': Operation not permitted
nslookup: write to '1.0.0.1': Operation not permitted
;; connection timed out; no servers could be reached

Ping works fine on ip addresses.

If I rollback to 3.10.0.9 everything works fine.
It doesn't appear to be a network lock problem, as I am using the old version with network_lock on and it works fine.
I even tried the newer version with network_lock off and it still did not work.

Sometimes activation fails

There are times when the container spins up the activation fails and all connections through the container are exposed.

I only noticed when I checked logs on portainer that sometimes when the system reboots or the container is manually restarted.

Is there a way to make the activation persist?

Feature request: HTTP controls (feature parity with glutun)

Any chance to add the HTTP controls?

      # TESTING
      - HTTP_CONTROL_SERVER_ADDRESS=:9988
      - HTTP_CONTROL_SERVER_LOG=on

Like this:
https://github.com/qdm12/gluetun-wiki/blob/main/setup/advanced/control-server.md

Allows for control by many outside applications, including Homepage polling functionality. Maybe start with a limitted set of functionality, gradually working toward full feature parity? Thanks!

"Warning: Extension udp revision 0 not supported, missing kernel module?"

I'm trying to run this container on a QNAP TVS-672N with QNAP OS version 5.0.2173 and I'm getting the following error:

Help improve ExpressVPN: Share crash reports, speed tests, usability diagnostics, and whether VPN connection attempts succeed. These reports never contain personally identifiable information. (Y/n) Preferred Protocol is lightway_udp.
LightwayCipher is chacha20.
Send Diagnostics is disabled.
Threat Manager is enabled.
Network Lock Mode is default.
Auto Connect is enabled.
If your VPN connection unexpectedly drops, internet traffic will now be
blocked by Network Lock to protect your privacy.

Connecting to Smart Location...
Connecting to USA - New York...
Unable to connect to USA - New York

   - Check your internet connection or try a different location.
   - Internet traffic is blocked to protect your privacy.
   - To retry the connection, type 'expressvpn connect'
   - To disconnect from the VPN and unblock internet traffic, type 'expressvpn disconnect'
Warning: Extension udp revision 0 not supported, missing kernel module?
iptables v1.8.8 (nf_tables): Could not fetch rule set generation id: Invalid argument

allowing dns server traffic in iptables: 192.168.1.1
Warning: Extension udp revision 0 not supported, missing kernel module?
iptables v1.8.8 (nf_tables): Could not fetch rule set generation id: Invalid argument

allowing dns server traffic in iptables: 1.1.1.1
Warning: Extension udp revision 0 not supported, missing kernel module?
iptables v1.8.8 (nf_tables): Could not fetch rule set generation id: Invalid argument

allowing dns server traffic in iptables: 8.8.8.8

I have this running on a PI, no problem so I know it's an issue with the QNAP OS. Any ideas?

Is there a way I can have this container use the network on another container? Perhaps I can run the ExpressVPN container on the PI and have my transmission container use that as its network?

Thanks!

raspberry pi version

I am trying to get this setup, and I see you mentioned to add the tag -armhf to be able to run it on raspberry pi, I am new to all of this, and where in the code would I add the tag to be able to run it on a raspberry?

service expressvpn restart failed !

Hi I need your help ...

I am running CasaOS on raspberry pi 5 , docker version 26 ,,, i am unable to get the expressvpn to work ..

i use the command below and keep getting either the container "exited" or it runs healthy but in the logs keep saying " service expressvpn restart failed !"

docker run --env=WHITELIST_DNS=192.168.1.1,1.1.1.1,8.8.8.8 --env=CODE=MyExpressvpnActivationCode --env=SERVER=smart --cap-add=NET_ADMIN --device=/dev/net/tun --privileged --detach=true --tty=true --name=expressvpn --publish 80:80 --env=PROTOCOL=lightway_udp misioslav/expressvpn:latest-bookworm /bin/bash

i tried many images like

misioslav/expressvpn:latest-bookworm
expressvpn:latest-bookworm

and the older images

Activation code doesn't work / Build for ARM64?

Hi,

I have an ARM64 device. I built the Docker image on another computer using the parameters:

--build-arg PLATFORM=armhf
--platform linux/arm/v7

I then ran the container on the ARM64 device, specifying my ExpressVPN activation code in the CODE environment variable. I get the expected warning about the platform mismatch ("The requested image's platform (linux/arm/v7) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested"), but the container starts up nonetheless. However, when looking at the logs, I see the following:

Restarting ExpressVPN service: expressvpnd.
spawn expressvpn activate
Enter activation code: 
Activating...
Unable to sign in. Please check your connection and try again.
Please activate your account.
Please activate your account.
Please activate your account.
Please activate your account.
Please activate your account.

As suggested in the other issue, I checked that the value of $CODE is correct inside the running container.

Any suggestions? Could this be related to the fact that I'm running an ARM v7 build on an ARM64 device? If so, would it be possible to get a build for ARM64?

Thanks!

Kernel Version is lower than minimum version of required kernel (4.9), network_lock will be disabled.

Suddenly I'm unable to connect to ExpressVPN, and am getting the following:

,spawn expressvpn activate


,Enter activation code: 

,Activating...

,Please activate your account.
,Please activate your account.
,Please activate your account.
,Kernel Version is lower than minimum version of required kernel (4.9), network_lock will be disabled.
,Please activate your account.
,Please activate your account.
,Please activate your account.```

Install issues

Good day

I am getting the device issue for dev/net/tun when I try and run the commands.

I am using proxmox with a docker container and portainer.

This is my first setup.

I am not sure how to solve this.

Thanks

healthcheck fails when there's an IPv6 address (an AAAA record) for the DDNS domain

• If there's an IPv6 address for the DDNS domain, it looks like the command currently used by healthcheck.sh will grab that preferentially to the IPv4 one
• The command that checks the ExpressVPN IP appears to grab the IPv4 address
• And so the two addresses will appear to be different no matter what, even if the expressvpn container is actually routing traffic through the host network

At the moment, this probably doesn't effect too many people, and I don't need an AAAA record on my DDNS domain. Creating this issue to note the behavior.

Run on Kubernetes

I'm trying to get it to run on Kubernetes on a Raspberry PI 64bit, but I can't get it to work.

Here is the k8s file:

apiVersion: apps/v1
kind: Deployment
metadata:
  name: expressvpn
spec:
  replicas: 1
  selector:
    matchLabels:
      app: expressvpn
  template:
    metadata:
      labels:
        app: expressvpn
    spec:
      containers:
        - name: expressvpn  
          image: misioslav/expressvpn:latest-arm64
          ports:
            - containerPort: 8080
          env:
            - name: CODE
              value: <CODE>
            - name: SERVER
              value: smart
            - name: PROTOCOL
              value: udp
            - name: CIPHER
              value: chacha20
          securityContext:
            allowPrivilegeEscalation: true
            capabilities:
              add:
                - NET_ADMIN
          volumeMounts:
            - name: tun-dev
              mountPath: /dev/net/tun
              readOnly: false
          stdin: true
          tty: true
      volumes:
      - name: tun-dev
        hostPath:
          path: /dev/net/tun

Here is a snippet of the logs:

Sat Sep  9 21:00:16 2023 /usr/sbin/expressvpnd --update-dns-config=static_resolv_conf tun0 1500 1556 10.60.0.86 10.60.0.85 init
DNS setting update type: up
2023/09/09 21:00:16 [I] updateDNSConfig: method="static_resolv_conf" script="up"
DNS setting update type: up, completed with error: link /etc/resolv.conf /etc/resolv.conf.expressvpn-orig: invalid cross-device link
2023/09/09 21:00:16 [T] acquiring /var/run/expressvpn/xv-update-dns-config.lock took 0.0ms
2023/09/09 21:00:16 [I] link: "/etc/resolv.conf" -> "/etc/resolv.conf.expressvpn-orig"
2023/09/09 21:00:16 [T] updateDNSConfig took 0.7ms
Sat Sep  9 21:00:16 2023 WARNING: Failed running command (--up/--down): external program exited with error status: 1
Sat Sep  9 21:00:16 2023 Exiting due to fatal error

Any idea what could be the issue?

Service failing to start - any ideas?

I restarted some containers over the weekend, and since then ExpressVPN hasn't started properly or connected. All I get is this:

I'm using latest - I see you made some changes to auto-update expressvpn. However, I also see the same with 3.60.0.4. I'm running the fix to create tun file structure.

Any ideas, or any hints on how to debug?

Trying to understand how the heathchecks.io integration works

I've read the documentation but I cannot work out how the healthchecks.io integration works.

I have tried both:
HEALTHCHECK=<ID>
and
HEALTHCHECK=https://hc-ping.com/<ID>
In both cases the container seems to start and show healthy, but in neither do I see any pings on my healthchecks.io status page

TIA

Running on RPI with kernel 6.x+ but it says my kernel version is below 4.9

When starting the container, it says the following

Kernel version is lower than the minimum required version (4.9). network_lock will be disabled.

I am going to try latest-armhf-bookworm and see if that helps as I was using latest-armhf before This did not help, and when entering the container cli, the kernel version is 6.1 on armhf-bookworm and latest-armhf, I believe it has something to do with the recent kernel version check you added

I believe this is where the problem may be

expressvpn/files/uname.sh

Line 9 in 3222b21

if (( major_version < 4 || (major_version == 4 && minor_version <= 9) )); then

In the meantime I have reverted to 3.48.0.4-armhf instead of the latest version to work around this

Leaking Original IP

I have 2 other dockers that are dependent on this express vpn docker and everytime I restart this VPN docker, this and other dependent dockers are leaking/using the actual IP and not the VPN IP for few seconds before it gets the VPN IP

"Please Activate Your Account"

Getting this error immediately after installing. My activation code was set in ENV variables.

Unable to connect to any location - Synology DSM 7.0.1-42218 Update 2

Hey,

I had some issues with my raspberry pi corrupting (unrelated to this project) so I figured I'd host some of my containers on my Synology NAS.

However I can't seem to connect to any location, it seems to activate fine, start going through the connection process before dropping before connection is complete.

Here is my docker compose
expressvpn:
image: misioslav/expressvpn:latest
container_name: expressvpn_denmark
restart: unless-stopped
ports: # ports from which container that uses expressvpn connection will be available in local network
- 8001:8989
- 8002:7878
- 8003:8686
- 8004:9696
- 8005:8005
- 8006:8006
- 8007:6881
- 8008:8080
environment:
- WHITELIST_DNS=1.1.1.1,8.8.8.8 # Comma seperated list of dns servers you wish to use and whitelist via iptables
- CODE=EO # Activation Code from ExpressVPN https://www.expressvpn.com/support/troubleshooting/find-activation-code/
- SERVER=dk # By default container will connect to smart location, list of available locations you can find below
- DDNS=bg # optional
- NETWORK=on #optional and set to on by default
- PROTOCOL=lightway_udp #optional set default to lightway_udp see protocol and cipher section for more information
- CIPHER=chacha20 #optional set default to chacha20 see protocol and cipher section for more information
cap_add:
- NET_ADMIN
devices:
- /dev/net/tun
stdin_open: true
tty: true
command: /bin/bash
privileged: true

Figuring this is a synology related issue as I've basically been running this same setup on raspberry pi (except for specific image) no problem, but if anyone has any suggestions that would be appreciated.

DNS issue

Hi!

When I set the network_mode to the expressvpn service on a clean ubuntu:latest, I do not get the DNS from the expressvpn container but the DNS from my host. Everything works perfectly within the expressvpn container. But I can't resolve anything in ubuntu container, when I cat /etc/resolv.conf I can confirm that the host DNS is being used.

Do you have any idea why this is so?

Always getting "network lock not available"

I'm not sure when this started happening or if it always has been, but whenever I start the container I see in the logs: network lock not available, this also happens if I restart the container. If I delete and recreate the container this occurs as well.

Log after a start and restart:

Restarting ExpressVPN service: expressvpnd.
spawn expressvpn activate


Enter activation code: 

Activating...

Activated.

Help improve ExpressVPN: Share crash reports, speed tests, usability diagnostics, and whether VPN connection attempts succeed. These reports never contain personally identifiable information. (Y/n) network lock not available
If your VPN connection unexpectedly drops, internet traffic will now be
blocked by Network Lock to protect your privacy.

Connecting to Smart Location...

Connecting to USA - Dallas...
Connecting to USA - Dallas...	1.0%
Connecting to USA - Dallas...	15.0%
Connecting to USA - Dallas...	37.5%
Connecting to USA - Dallas...	75.0%
Connecting to USA - Dallas...	85.0%
Connecting to USA - Dallas...	100.0%
Connected to USA - Dallas

   - To check your connection status, type 'expressvpn status'.
   - If your VPN connection unexpectedly drops, internet traffic will be blocked to protect your privacy.
   - To disable Network Lock, disconnect ExpressVPN then type 'expressvpn preferences set network_lock off'.
Restarting ExpressVPN service: expressvpnd.
spawn expressvpn activate


Already activated. Logout from your account (y/N)? 

N

network lock not available
Connecting to Smart Location...

Connecting to USA - Dallas...
Connecting to USA - Dallas...	1.0%
Connecting to USA - Dallas...	15.0%
Connecting to USA - Dallas...	37.5%
Connecting to USA - Dallas...	75.0%
Connecting to USA - Dallas...	85.0%
Connecting to USA - Dallas...	100.0%
Connected to USA - Dallas

   - To check your connection status, type 'expressvpn status'.
   - If your VPN connection unexpectedly drops, internet traffic will be blocked to protect your privacy.
   - To disable Network Lock, disconnect ExpressVPN then type 'expressvpn preferences set network_lock off'.

My compose file:

---
version: "2.1"
services:

  expressvpn:
    image: misioslav/expressvpn:latest
    container_name: expressvpn
    restart: unless-stopped
    ports: # ports from which container that uses expressvpn connection will be available in local network
      - xxxx:xxxx
      - xxxx:xxxx
      - xxxx:xxxx
      - xxxx:xxxx
      - xxxx:xxxx
    dns:
      - 1.1.1.1
      - 1.0.0.1
      - 2606:4700:4700::1111
      - 2606:4700:4700::1001
    environment:
      - CODE=${CODE} # Activation Code from ExpressVPN https://www.expressvpn.com/support/troubleshooting/find-activation-code/
      - SERVER=SMART # By default container will connect to smart location, list of available locations you can find below
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    stdin_open: true
    tty: true
    command: /bin/bash
    privileged: true

Any way to build a socks5 proxy server on this?

Hello, thanks so much for making this thing, I installed it successfully in my VPS!

sorry in advance for asking this stupid question, im still new to this thing

but is there a way i can build a socks5 server inside this docker or any other ways?

I want one of my PC to connect to expressvpn from a socks5 proxy

for some reason i cannot just install expressvpn on my machine, and when I install expressvpn in my vps, i lost it forever, cannot ssh to it anymore.

So i think may be this expressvpn running in docker can help me in this case.

any ideas?

Error: Could not resolve host

This is the error I get... ExpressVPN on it's own does indeed connect to the correct IP as I verified. Transmission, on its own as host connects and works fine but when I change Transmission network to container:expressvpn I get this...

curl ifconfig.io

curl: (6) Could not resolve host: ifconfig.io

if ExpressVPN fails to connect, traffic will be routed through the host network

Making a separate issue for this after all :)

If ExpressVPN fails to connect, e.g. because an invalid CODE was passed, and if healthcheck passes (e.g. because no IP or DDNS was passed or there happens to be an AAAA record for the given DDNS domain), traffic will be routed through the host network without warning.

The easiest fix would be to change this line

expressvpn/files/start.sh

Line 38 in 5245f4c

expressvpn connect $SERVER

to

expressvpn connect $SERVER || exit

If ExpressVPN fails to connect, it should exit non-zero, which with this change would fail the container startup (like we want). If ExpressVPN succeeds, network lock should be active, and we shouldn't have to worry about it after that (hopefully).

For now, I've worked around this by adding a line to the command for this container in my compose.yaml

expressvpn status | grep -i '^\S*connected to' || exit

This works just as well for now (assuming the output of expressvpn status doesn't change too much) and doesn't require any changes to the container.

Full compose.yaml for reference, now that i've got it working

volumes:
  share:

services:
  ddclient:
    image: linuxserver/ddclient:latest
    container_name: ddclient
    restart: unless-stopped
    network_mode: host
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
    volumes:
      # - /path/to/ddclient/config:/config # TODO

  expressvpn:
    image: misioslav/expressvpn:latest-arm64
    container_name: expressvpn
    restart: unless-stopped
    ports:
      - 8080:8080
    environment:
      CODE: <expressvpn code>
      DDNS: <ddns domain>
    volumes:
      - share:/share
    tty: true
    stdin_open: true
    command:
      - /bin/bash
      - -c
      - |
        expressvpn status | grep -i '^\S*connected to' || exit
        cp /etc/resolv.conf /share/resolv.conf || exit
        exec bash
    cap_add:
      - NET_ADMIN
    devices:
      - /dev/net/tun
    privileged: true

  qbittorrent:
    image: linuxserver/qbittorrent:latest
    container_name: qbittorrent
    restart: unless-stopped
    network_mode: service:expressvpn
    depends_on:
      expressvpn:
        condition: service_healthy
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - share:/share:ro
    #   - /path/to/qbittorrent/appdata:/config # TODO
    #   - /path/to/downloads:/downloads # TODO
    tty: true
    stdin_open: true
    command:
      - /bin/bash
      - -c
      - |
        cp /share/resolv.conf /etc/resolv.conf || exit
        exec bash

client container seems to bypass expressvpn

Hi, looking for some help. I am using your expressvpn image in a composition. The container that uses the expressvpn service is spinning up fine and ipinfo.io is showing the details as being connected via vpn (basically shows the same as the epressvpn container which is what you would expect). I am using get_iplayer and no matter what I do it seems to somehow bypass the vpn network. I know this because the responses I am getting from iplayer indicate that they are rejecting the requests because of location.. its the oddest thing. I can follow the same model using a nordvpn image and its fine (I need to move off nordvpn as my subcription is about to expire). Have you seen anything like this before?

ExpressVPN won't activate.

System running Docker: MacMini M2
MacOS: 13.3.1 (a)

Hello! Since last week, my ExpressVPN container isn't activating. I've tried deleting the container, image, and reinstalling but still run into the same issue. I've also tried to manually activate ExpressVPN via the container console but that fails as well.

I did notice that I received the following message in terminal after starting the container...

WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
9c1f7fc38f5e25052a58f75602cdf3f5fb76bbd2d233566ac0cbb6ce8e11d204

I don't recall seeing this particular warning when I originally installed and started the ExpressVPN container. Apologies if the answer to resolving this is obvious. I am still relatively new to working with Docker. Any guidance towards a fix would be much appreciated!

Unable to connect / Unable to create tun device

All of a sudden I am getting this error when trying to connect to expressvpn inside docker container in Synology NAS.

2022-01-02T18:33:18.452+0000 Attempting to create tun device ''
2022-01-02T18:33:18.452+0000 failed to open /dev/net/tun: No such file or directory
2022-01-02T18:33:18.452+0000 Unable to create tun device
2022-01-02T18:33:18.452+0000 process_outside_packet: error config network
2022-01-02T18:33:18.452+0000 he_execute: starting /usr/sbin/expressvpnd --update-dns-config=static_resolv_conf
2022-01-02T18:33:18.500+0000 he_execute: process exited 0 (signal 0)
2022-01-02T18:33:18.500+0000 Lightway DISCONNECTED (disconnect_and_stop).
2022-01-02T18:33:18.500+0000 Lightway STOPPED
2022-01-02T18:33:18.500+0000 Lightway FINISHED
Disconnected with error: HE_ERR_CALLBACK_FAILED

Any suggestions?

run as non-privleged

I recognize this is not really a issue, more of a request of a feature request. I'm sure there are some very specific reasons why the container needs to run as privileged but I'm hoping there's a way to avoid this requirement or configure the host to bypass this? Even if I can just restrict the privileges granted would be a nice improvement but I don't know what to create explicate exceptions for. Any chance you can provide some insight?

After updating to latest version I have issues with network lock

Having difficulties getting the latest docker container running in Portainer to work.
Any clues?

`
Restarting ExpressVPN service: expressvpnd.
spawn expressvpn activate

Enter activation code:
Activating...
Activated.

Help improve ExpressVPN: Share crash reports, speed tests, usability diagnostics, and whether VPN connection attempts succeed. These reports never contain personally identifiable information. (Y/n) network lock mode: default
If your VPN connection unexpectedly drops, internet traffic will now be
blocked by Network Lock to protect your privacy.

Connecting to Smart Location...

Connecting to Germany...
Unable to connect to Germany

• Check your internet connection or try a different location.
• Internet traffic is blocked to protect your privacy.
• To retry the connection, type 'expressvpn connect'
• To disconnect from the VPN and unblock internet traffic, type 'expressvpn disconnect'
  `

Feature request: Add Net-tools

Can we please add net-tools to the image? Very small and easy to add and gives a lot of tools. Thank you

Building image

Hello,
I forked this repo and want to build my own image. I am new to docker so forgive me if i made an obvious mistake. I tried using command "docker build -t expressvpn" but then after running it I get this error inside the container:
: no mount point specified. cp: cannot stat '/etc/resolv.conf.bak': No such file or directory /etc/init.d/expressvpn: line 207: log_action_msg: command not found ": no such file or directoryvpn/activate.sh Cannot connect to expressvpnd daemon. It seems that the expressvpn daemon is not running. Please run "sudo service expressvpn restart" to start it. If the problem persists, please contact us. Cannot connect to expressvpnd daemon. It seems that the expressvpn daemon is not running. Please run "sudo service expressvpn restart" to start it. If the problem persists, please contact us. /expressvpn/start.sh: line 10: $'\r': command not found

Could someone please help me with building this image?
Thanks!

QNAP - Unable to connect issues.

Hey there i hope you well.

I am getting this odd issues i see was reported before but there wasn't a resolution to it. i have attached the log anything else that might help?

Regards
Ross

Restarting ExpressVPN service: expressvpnd.
spawn expressvpn activate
Want extra privacy? Try Threat Manager. While your VPN is connected, Threat Manager adds an extra layer of privacy by blocking apps and websites from sharing your activity with third-party trackers or communicating with other malicious sites.

To enable Threat Manager, type 'expressvpn preferences set block_trackers true'.

Enter activation code:
Activating...
Activated.
Help improve ExpressVPN: Share crash reports, speed tests, usability diagnostics, and whether VPN connection attempts succeed. These reports never contain personally identifiable information. (Y/n) Preferred Protocol is lightway_tcp.
LightwayCipher is chacha20.
Send Diagnostics is disabled.
Threat Manager is enabled.
Network Lock Mode is default.
Auto Connect is enabled.
If your VPN connection unexpectedly drops, internet traffic will now be
blocked by Network Lock to protect your privacy.

Connecting to Netherlands - Amsterdam...
Unable to connect to Netherlands - Amsterdam

• Check your internet connection or try a different location.
• Internet traffic is blocked to protect your privacy.
• To retry the connection, type 'expressvpn connect'
• To disconnect from the VPN and unblock internet traffic, type 'expressvpn disconnect'
  Warning: Extension udp revision 0 not supported, missing kernel module?
  iptables v1.8.9 (nf_tables): Could not fetch rule set generation id: Invalid argument
  allowing dns server traffic in iptables: 192.168.1.1
  Warning: Extension udp revision 0 not supported, missing kernel module?
  iptables v1.8.9 (nf_tables): Could not fetch rule set generation id: Invalid argument
  allowing dns server traffic in iptables: 1.1.1.1
  Warning: Extension udp revision 0 not supported, missing kernel module?
  iptables v1.8.9 (nf_tables): Could not fetch rule set generation id: Invalid argument
  allowing dns server traffic in iptables: 8.8.8.8