[GH-ISSUE #2375] macOS: AmneziaVPN does not reliably route Codex.app traffic while ChatGPT.app works on the same VPN #1048

Open
opened 2026-10-13 20:33:29 +00:00 by bsakaguchi · 1 comment
Owner

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

Hi,

I want to report a macOS routing/tunnel issue in AmneziaVPN.

Environment:
AmneziaVPN 4.8.14.5
macOS 26.2
Apple Silicon
same machine, same network, same VPN server

Problem:
ChatGPT.app works through AmneziaVPN
Codex.app does not worуk correctly through AmneziaVPN
the same Codex.app works through another tunnel client on the same machine

So this does not look like a general network problem.

What I see in Amnezia service logs:
"Created wireguard interface utun6"
repeated "Checking for handshake..."
repeated "awaiting ..."
later route changes involving another tunnel interface:
"Route update via utun7"
"Updating default route via utun7"

This suggests a macOS routing/interf ace tracking problem, especially in multi-utun conditions.

Expected behavior:

  • if Amnezia reports connected, traffic should stay on the correct tunnel interface
  • route ownership should remain stable
  • handshake failure or route takeover should be visible to the user

Possibly related:
#924
#1223

Please investigate:
macOS route monitor logic
utun interface ownership/detection
handshake completion state vs reported connected state
route changes after tunnel creation

Thanks.

Originally created by @Mamaysky on GitHub (Mar 20, 2026). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/2375 Hi, I want to report a macOS routing/tunnel issue in AmneziaVPN. Environment: AmneziaVPN 4.8.14.5 macOS 26.2 Apple Silicon same machine, same network, same VPN server Problem: ChatGPT.app works through AmneziaVPN Codex.app does not worуk correctly through AmneziaVPN the same Codex.app works through another tunnel client on the same machine So this does not look like a general network problem. What I see in Amnezia service logs: "Created wireguard interface utun6" repeated "Checking for handshake..." repeated "awaiting ..." later route changes involving another tunnel interface: "Route update via utun7" "Updating default route via utun7" This suggests a macOS routing/interf ace tracking problem, especially in multi-utun conditions. Expected behavior: - if Amnezia reports connected, traffic should stay on the correct tunnel interface - route ownership should remain stable - handshake failure or route takeover should be visible to the user Possibly related: #924 #1223 Please investigate: macOS route monitor logic utun interface ownership/detection handshake completion state vs reported connected state route changes after tunnel creation Thanks.
Author
Owner

@dilp79 commented on GitHub (Apr 2, 2026):

i have same issue on Windows - chatGPT web session works ok, but codex CLI in WSL does not work. Also claude CLI does not work , but claud web site and claude desktop works ok. Everything else (youtube, facebook, speedtest etc) works fine
AmneziaVPN (AmneziaVPN_4.8.14.5_x64), protocol AmneziaWG version 2.

<!-- gh-comment-id:4180457433 --> @dilp79 commented on GitHub (Apr 2, 2026): i have same issue on Windows - chatGPT web session works ok, but codex CLI in WSL does not work. Also claude CLI does not work , but claud web site and claude desktop works ok. Everything else (youtube, facebook, speedtest etc) works fine AmneziaVPN (AmneziaVPN_4.8.14.5_x64), protocol AmneziaWG version 2.
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#1048
No description provided.