[GH-ISSUE #1618] [FEATURE] Multi-Hop VPN #676

Open
opened 2026-10-13 20:26:21 +00:00 by bsakaguchi · 5 comments
Owner

Originally created by @ghost on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1618

Connection > Server 1 > Server 2
(self-explaning)

Originally created by @ghost on GitHub (May 24, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1618 Connection > Server 1 > Server 2 **(self-explaning)**
Author
Owner

@Noxius87 commented on GitHub (Jun 2, 2025):

Can you explain more about what the issue is?

<!-- gh-comment-id:2932075356 --> @Noxius87 commented on GitHub (Jun 2, 2025): Can you explain more about what the issue is?
Author
Owner

@ghost commented on GitHub (Jun 3, 2025):

Can you explain more about what the issue is?

Its not issue, its suggestion, there's no other way to make suggestions

<!-- gh-comment-id:2934127505 --> @ghost commented on GitHub (Jun 3, 2025): > Can you explain more about what the issue is? Its not issue, its suggestion, there's no other way to make suggestions
Author
Owner

@Serathin commented on GitHub (Mar 30, 2026):

I did something similar

  1. I raised 2 vps
  2. I installed amnesia on the first vps
  3. I configured traffic proxying on the second vps to the first vps
  4. When I add a new user, I edit the config and replace the endpoint with the second vps
<!-- gh-comment-id:4152304187 --> @Serathin commented on GitHub (Mar 30, 2026): I did something similar 1) I raised 2 vps 2) I installed amnesia on the first vps 3) I configured traffic proxying on the second vps to the first vps 4) When I add a new user, I edit the config and replace the endpoint with the second vps
Author
Owner

@chykon commented on GitHub (May 5, 2026):

A possible implementation could be implemented as an additional service, optionally installed on the server (like Amnezia DNS).

The setup method could be as follows:

  • in the Additional Services tab, select "Multi-Hop Setup"
  • enter the data (IP/login/password as when first setting up Amnezia) for the second server (it might be worth requiring that Amnezia be configured on the second server)
  • select which server traffic will be redirected to which (a bidirectional option might even be useful: traffic from S1 is redirected to S2, and traffic from S2 is redirected to S1 - of course, it's important to avoid traffic loops)
  • select the protocol for communication between servers (essentially the same as for clients)
  • start server setup
  • once setup is complete, enjoy your multi-hop configuration
<!-- gh-comment-id:4378051814 --> @chykon commented on GitHub (May 5, 2026): A possible implementation could be implemented as an additional service, optionally installed on the server (like Amnezia DNS). The setup method could be as follows: * in the Additional Services tab, select "Multi-Hop Setup" * enter the data (IP/login/password as when first setting up Amnezia) for the second server (it might be worth requiring that Amnezia be configured on the second server) * select which server traffic will be redirected to which (a bidirectional option might even be useful: traffic from S1 is redirected to S2, and traffic from S2 is redirected to S1 - of course, it's important to avoid traffic loops) * select the protocol for communication between servers (essentially the same as for clients) * start server setup * once setup is complete, enjoy your multi-hop configuration
Author
Owner

@voipp commented on GitHub (Jun 3, 2026):

Any updates?

<!-- gh-comment-id:4610574838 --> @voipp commented on GitHub (Jun 3, 2026): Any updates?
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#676
No description provided.