AdGuardVPNCLI icon indicating copy to clipboard operation
AdGuardVPNCLI copied to clipboard

After some time VPN goes to Reconnecting state

Open Alex-302 opened this issue 11 months ago • 1 comments

Please answer the following question for yourself before submitting an issue

  • [x] I checked to make sure that this issue has not already been filed

AdGuard VPN CLI version

1.2.10 nightly

Environment

  • OS: Synology DSM 7.2.1-69057 Update 6 Linux version 4.4.302+ (root@build5) (gcc version 12.2.0 (GCC) ) #69057 SMP Fri Jan 12 17:02:28 CST 2024

  • Architecture: x86_64

    HTOP screenshot

    Image

VPN config

Location: Ukraine, Kyiv

Current configuration:
        Data directory: /root/.local/share/adguardvpn-cli
        Mode: socks
        SOCKS port: 1080
        SOCKS host: 192.168.88.102
        SOCKS username: adg
        DNS upstream: https://d.adguard-dns.com/dns-query/xxxxxxx
        Tunnel routing mode: none
        Change system DNS: on
        Crash reporting: on
        Update channel: NIGHTLY
        Use QUIC: off
        Show hints: on
        Debug logging: on
        Show notifications: Default (off)

Issue Details

Steps to reproduce:

  1. Run AdGuard VPN in proxy mode
  2. Make requests through the proxy during one day (or more)
  3. After a while (a few hours or more), the proxy stops responding. After disconnect and connect, it works again until next fail.

No connected clients.

I use a simple script to make requests every 5 seconds (change IP:port and login:pwd in she script if you will use it) check_vpncli_socks5.zip

Current output

Screenshot 1

Image

Logs: adguardvpn-cli-logs_18-01-2025_14-00.zip

Expected Behavior

Does not disconnect, or reconnects successful.

Actual Behavior

Start time: 16:43:57 Last successful request: 12:05:28 Current time: 13:45

During this session clients did not use this proxy. I use CURL request in loop to check the proxy curl --proxy socks5h://192.168.88.102:1080 -U adg:adg https://adguard.com/whoami.txt

Screenshots

No response

Additional Information

No response

Alex-302 avatar Jan 18 '25 12:01 Alex-302

Also having the same issue. There seems to be some sort of issue with the Socks5 proxy that makes it required to manually restart the vpn after a certain period of time for proper functioning.

Eollone avatar Mar 03 '25 09:03 Eollone