OpenVPN worked 1 week, rebooted server, not working anymore

  • I pretty much followed this guide:

    https://dbtechreviews.com/2020…-openmediavault-5-docker/


    1. It worked great week first week of install
    2. Performed a weekly restart
    3. Failed to connect, noticed the container was not started, so I started OpenVPN Container
    4. Still failed to connect
    5. Collected logs below

    Couple notes:

    IP of my server is 192.168.85.200 (yes, 1194 correctly FWD'ed on Router, I have not touched network settings)

    Using DuckDNS, My IP didn't change, still valid

    I can't even connect on same wifi using OpenVPN from phone (no wifi)

    Including screenshot of a couple Docker/Portainer containers including OVPN if that is helpful (the IP assignment in Portainer sill confuses me, does it look normal?)



  • Does it still have the NET_ADMIN Capability?


    Code
    Thu Jan 20 03:15:28 2022 /sbin/ip route del 192.168.254.0/24
    
    RTNETLINK answers: Operation not permitted
    Thu Jan 20 03:15:28 2022 ERROR: Linux route delete command failed: external program exited with error status: 2
    Thu Jan 20 03:15:28 2022 /sbin/ip route del 192.168.255.0/24
    RTNETLINK answers: Operation not permitted



    docker run -v $OVPN_DATA:/etc/openvpn -d -p 1194:1194/udp --cap-add=NET_ADMIN kylemanna/openvpn



    A reboot will not recreate the copntainer, but only start it. If in doubt, remove the container and rereate it.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • Sure, I can recreate it, just trying to save myself 10-15 mins, but spending more time troubleshooting. I'll have to do that later.

    I was able to run the suggested command FYI:

    BTW - Only OPENVPN is using port 1194. idk why it says already allocated

    Code
    root@deathstar:~# docker run -v $OVPN_DATA:/etc/openvpn -d -p 1194:1194/udp --cap-add=NET_ADMIN kylemanna/openvpn
    8cd700a66ff48e08f3e0ddd38ab3d46f4876485ed1f58fcc07136ea20faebe48
    docker: Error response from daemon: driver failed programming external connectivity on endpoint dazzling_wilson (53fcf28e0b7c6965d6442de0c6f784ae61cd818c443ac1eacf2bee10562a5261): Bind for 0.0.0.0:1194 failed: port is already allocated.
  • There is a container running. You have to top / rm it first.

    If you got help in the forum and want to give something back to the project click here (omv) or here (scroll down) (plugins) and write up your solution for others.

  • I (the IP assignment in Portainer sill confuses me, does it look normal?)

    172.* IP addresses belong to the container networking and are normal.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    • Offizieller Beitrag

    Not directly related to your query, but you might want to take a look here

    [How-To] Install Wireguard (VPN) in docker, server mode

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!