[GH-ISSUE #2386] AmneziaVPN app does not handle CNAMEs properly for Self-Hosted VPSs #1056

New issue

Open

opened 2026-10-13 20:33:35 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-13 20:33:35 +00:00

Owner

Originally created by @ArkBrj on GitHub (Mar 22, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2386

I just discovered that AmneziaVPN app (on Windows) has a weird quirk when it is used to set up a self-hosted VPS.
In short, it does not deal properly with VPS DNS names that are CNAME's (aliases).
I am experimenting at home where I do not have a static IP, so I use some DDNS service to map myhost.freeddns.org to my dynamic IP.
On top of that I have a CNAME entry to map my better looking domain name to myhost.freeddns.org.
Like this:
mynicehostname.mycooldomain.com --(CNAME)--> myhost.freeddns.org --(A)--> NNN.NNN.NNN.NNN
AmneziaVPN app is able to connect to my VPS if I specify NNN.NNN.NNN.NNN (the external IP address) or myhost.freeddns.org but not if I specify mynicehostname.mycooldomain.com.
In the latter case it displays a very misleading error "ErrorCode 300: SSH request was denied".
Of course, in all 3 cases I provide the same port/login name/SSH private key.
In the failing case I do not see any attempts to connect to my VPS in its logs. Seems like AmneziaVPN app does not even try to connect.
The repro procedure should be obvious - just create a CNAME DNS record to an existing host name and try to use it in the app.

Originally created by @ArkBrj on GitHub (Mar 22, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2386 I just discovered that AmneziaVPN app (on Windows) has a weird quirk when it is used to set up a self-hosted VPS. In short, it does not deal properly with VPS DNS names that are CNAME's (aliases). I am experimenting at home where I do not have a static IP, so I use some DDNS service to map myhost.freeddns.org to my dynamic IP. On top of that I have a CNAME entry to map my better looking domain name to myhost.freeddns.org. Like this: mynicehostname.mycooldomain.com --(CNAME)--> myhost.freeddns.org --(A)--> NNN.NNN.NNN.NNN AmneziaVPN app is able to connect to my VPS if I specify NNN.NNN.NNN.NNN (the external IP address) or myhost.freeddns.org but not if I specify mynicehostname.mycooldomain.com. In the latter case it displays a very misleading error "ErrorCode 300: SSH request was denied". Of course, in all 3 cases I provide the same port/login name/SSH private key. In the failing case I do not see any attempts to connect to my VPS in its logs. Seems like AmneziaVPN app does not even try to connect. The repro procedure should be obvious - just create a CNAME DNS record to an existing host name and try to use it in the app.

bsakaguchi referenced this issue

2026-10-13 21:19:50 +00:00

[PR #1056] [MERGED] Add connection checking for WG/AWG via logs #2220