After deploying on the cloud server, it is inaccessible when it is turned on, but accessible when it is turned off.

AdguardTeam / AdGuardVPNCLI

AdGuard VPN command-line version

https://adguard-vpn.com/

42 stars 0 forks source link

After deploying on the cloud server, it is inaccessible when it is turned on, but accessible when it is turned off. #31

Closed chiheye closed 6 days ago

chiheye commented 2 weeks ago

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.0

Environment

OS: centos stream 9
Architecture: x86-64

Issue Details

Steps to reproduce: 1.The service can be started and stopped normally. 2.Deployed on a cloud server.

Expected Behavior

No response

Actual Behavior

The Docker container requires access to the internet, hence it is deployed on a cloud server.

Screenshots

No response

Additional Information

No response

sfionov commented 1 week ago

@chiheye Hello! Can you please specify your setup? Where adguardvpn-cli is running - on host or inside Docker?

aliafshany commented 1 week ago

@chiheye it's because you are using it in TUN mode. Use SOCKS5 in order to access your server.

chiheye commented 1 week ago

@chiheye Hello! Can you please specify your setup? Where adguardvpn-cli is running - on host or inside Docker?

inside Docker

chiheye commented 1 week ago

@chiheye it's because you are using it in TUN mode. Use SOCKS5 in order to access your server.

I tried switching modes to TUN and SOCKS5, but neither could access the Docker container's port properly. If I disconnect from AdGuardVPNCLI, access is normal. The same situation occurs when I test it on my local laptop.