[GH-ISSUE #125] Add action to set up exit VPN on the remote server #68

New issue

Closed

opened 2026-10-13 21:03:16 +00:00 by bsakaguchi · 1 comment

bsakaguchi commented

2026-10-13 21:03:16 +00:00

Owner

Originally created by @greppy-ubuntu-floppy-5297 on GitHub (Mar 22, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/125

Problem

I started using AmneziaVPN during the first wave of blocks and initially ran my own server. Later, when the paid subscription became available, I switched to it for simplicity. After the latest blocking wave (March 2026), many of my non-technical contacts lost the ability to use VPNs.

I’m now considering running my own server again, since the 7-device limit is not enough. However, there is an important constraint:
I don’t want to be legally or operationally responsible for user activity (e.g., torrents or abuse) from my server. To address this, I want to route all outgoing traffic through a second VPN (exit VPN).

Context

I understand adding new features is costly and complex. Amnezia client already supports multiple server setup strategies. An “exit VPN” layer seems like a natural extension. Amnezia’s main strength is censorship bypass, not privacy/anonymity. It makes sense to combine it with a dedicated privacy VPN provider.

Proposal

Allow configuring an exit VPN on the server, for example:

Import WireGuard or OpenVPN config (via QR / paste / file) . Amnezia UI components and logic can be reused.
Automatically set up the VPN client on the server.
Route all outgoing traffic through Exit VPN

Resulting architecture:

Client → Server ( Amnezia → Exit VPN) → Internet

Benefits

Reduces legal responsibility for server owners
Enables safe multi-user setups
Complements Amnezia’s censorship-bypass focus with strong privacy layer

Originally created by @greppy-ubuntu-floppy-5297 on GitHub (Mar 22, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/125 ### Problem I started using AmneziaVPN during the first wave of blocks and initially ran my own server. Later, when the paid subscription became available, I switched to it for simplicity. After the latest blocking wave (March 2026), many of my non-technical contacts lost the ability to use VPNs. I’m now considering running my own server again, since the 7-device limit is not enough. However, there is an important constraint: **I don’t want to be legally or operationally responsible for user activity (e.g., torrents or abuse) from my server.** To address this, I want to route all outgoing traffic through a second VPN (exit VPN). ### Context I understand adding new features is costly and complex. Amnezia client already supports multiple server setup strategies. An “exit VPN” layer seems like a natural extension. Amnezia’s main strength is censorship bypass, not privacy/anonymity. It makes sense to combine it with a dedicated privacy VPN provider. ### Proposal Allow configuring an exit VPN on the server, for example: 1. Import WireGuard or OpenVPN config (via QR / paste / file) . Amnezia UI components and logic can be reused. 2. Automatically set up the VPN client on the server. 3. Route all outgoing traffic through Exit VPN Resulting architecture: ``` Client → Server ( Amnezia → Exit VPN) → Internet ``` ### Benefits Reduces legal responsibility for server owners Enables safe multi-user setups Complements Amnezia’s censorship-bypass focus with strong privacy layer

bsakaguchi closed this issue

2026-10-13 21:03:16 +00:00

bsakaguchi commented

2026-10-13 21:03:17 +00:00

Author

Owner

@greppy-ubuntu-floppy-5297 commented on GitHub (Mar 24, 2026):

wrong repo

@greppy-ubuntu-floppy-5297 commented on GitHub (Mar 24, 2026): wrong repo

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/amneziawg-go#68

No description provided.

Rows
Columns