[GH-ISSUE #3031] Standard client creation via GUI doesn't work after changing the server port (e.g. when moving to 443/udp) #1390

Open
opened 2026-10-13 20:41:25 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @koster99-blip on GitHub (Aug 24, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/3031

Problem:

After the server port is changed manually (for example, when moving to 443/udp, see issue #3029 about blocking by mobile carriers), the standard "add new client" function in the desktop client with admin rights stops working correctly. It looks like the client creation logic in the GUI is hardcoded to the default port and doesn't account for the server already being configured on a different port.

As a result, the only working way to add a new client after changing the port is to manually edit the configuration on the server (via scripts, directly in config files and the client table), completely bypassing the graphical interface.

Why this matters:

This creates a contradiction. To get the VPN working at all for users on mobile carriers in strict-DPI jurisdictions (see #3029), an administrator has to change the port. But once that's done, the standard user management tools stop working, and any further administration requires programming skills and direct server access, rather than just using the app.

Port 443/udp isn't the only layer that ends up requiring manual setup: in some network conditions it's also necessary to intercept and redirect DNS traffic (port 53) to get a fully working connection. This is another layer of manual configuration that the standard GUI doesn't support or account for.

This makes the product practically inaccessible to administrators without a technical background, in exactly the conditions where the VPN is needed most.

Suggestion:

Have the client creation function in the GUI read the server's current port from its actual configuration instead of relying on the default, or allow the port to be explicitly specified when adding a client.

Originally created by @koster99-blip on GitHub (Aug 24, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/3031 Problem: After the server port is changed manually (for example, when moving to 443/udp, see issue #3029 about blocking by mobile carriers), the standard "add new client" function in the desktop client with admin rights stops working correctly. It looks like the client creation logic in the GUI is hardcoded to the default port and doesn't account for the server already being configured on a different port. As a result, the only working way to add a new client after changing the port is to manually edit the configuration on the server (via scripts, directly in config files and the client table), completely bypassing the graphical interface. Why this matters: This creates a contradiction. To get the VPN working at all for users on mobile carriers in strict-DPI jurisdictions (see #3029), an administrator has to change the port. But once that's done, the standard user management tools stop working, and any further administration requires programming skills and direct server access, rather than just using the app. Port 443/udp isn't the only layer that ends up requiring manual setup: in some network conditions it's also necessary to intercept and redirect DNS traffic (port 53) to get a fully working connection. This is another layer of manual configuration that the standard GUI doesn't support or account for. This makes the product practically inaccessible to administrators without a technical background, in exactly the conditions where the VPN is needed most. Suggestion: Have the client creation function in the GUI read the server's current port from its actual configuration instead of relying on the default, or allow the port to be explicitly specified when adding a client.
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
amnezia-vpn/amnezia-client#1390
No description provided.