Inactivity timeout

[FunDeckHermit]

Hi

I've been trying to use the docker container to connect to a CyberGhost VPN server. The VPN connection seems to work, only after a minute the container restarts.

Inactivity timeout (--ping-exit), exiting
Closing socket

This is the log I get: link

Using this docker-compose file:

version: '3.4'

services:
  vpn:
    container_name: "vpn"
    image: dperson/openvpn-client
    # cap_add, security_opt, and volume required for the image to function
    cap_add:
      - net_admin
    environment:
      TZ: 'Europe/Amsterdam'
      VPN_AUTH: 'hidden;hidden'
      ROUTE: "192.168.1.0/24"
    networks:
      - default
    # if using '-d' or 'DNS' you can't enable the `read_only: true` option
    read_only: true
    tmpfs:
      - /run
      - /tmp
    restart: unless-stopped
    security_opt:
      - label:disable
    stdin_open: true
    tty: true
    ports:
      - 1080:1080
      - 8112:8112
    volumes:
      - /dev/net:/dev/net:z
      - ./vpn:/vpn

[dperson]

Do you have a message in docker logs similar to Peer Connection Initiated? If you don't you're not ever connecting.

[FunDeckHermit]

Hello @dperson,

The hastebin I supplied is all I get when running docker-compose up. Then I suspect the CyberGhost VPN files are incorrect.

I have including an enabled VPN configuration for testing purposes. Username: p3Hb6gGLGU, Password: 7G4dMFpda9 dperson_openvpn.zip The configuration will work untill the 22nd of may.

[feickertm]

I am having the same Problem. I think it is a configuration problem. The recently changed their server configurations and now like you I am having alot of warings in the openvpn logs. I have already created a support ticket for that. If anything new comes up I will let you know.

[karan]

I was having the same issue with PIA, and after switching to nextgen configs (instead of "current"), so far it's been stable.

[NinoSkopac]

@karan Thank you 💟