amnezia-vpn/amnezia-client

Fork 0

mirror of https://github.com/amnezia-vpn/amnezia-client.git synced 2026-10-15 05:42:07 +00:00

[GH-ISSUE #1347] Split tunneling is not available by IP/hostname for imported WG config on macOS client: "default server does not support split tunneling function" #542

New issue

Closed

opened 2026-10-13 20:23:49 +00:00 by bsakaguchi · 5 comments

bsakaguchi commented

2026-10-13 20:23:49 +00:00

Owner

Originally created by @softhoz on GitHub (Jan 6, 2025).
Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1347

Describe the bug
Split tunneling is not available by IP/hostname for imported WG config on macOS client: "default server does not support split tunneling function". I have a hosted WG server and imported client config to amneziaVPN client. It works fine, but split tunneling is not available at all.

To Reproduce
Steps to reproduce the behavior:

Open AmneziaVPN client
Click on '+' button
Click 'File with connection settings' to import your WG config file
Select config file for import and enable WG obfuscation
Click 'Split tunneling enabled' button on the 'Connect' screen with the newly imported config
Check that 'Split tunneling on the server' has status 'Enabled'
Click 'Site-based split tunneling'

Expected behavior
Toggle switch is available and hostname/IPs can be added to the list

Actual behavior
Toggle switch is grey, warning pop-ups "default server does not support split tunneling function"

Screenshots

Desktop (please complete the following information):

OS: macOS Sequoia 15.2 on Apple M4

** AmneziaVPN client version

4.8.2.3

Additional context
AllowedIPs options in the WG client config do not work as well, allowed IPs (other than 0.0.0.0/0) become unreachable and other IPs work but with no tunneling at all

Originally created by @softhoz on GitHub (Jan 6, 2025). Original GitHub issue: https://github.com/amnezia-vpn/amnezia-client/issues/1347 **Describe the bug** Split tunneling is not available by IP/hostname for imported WG config on macOS client: "default server does not support split tunneling function". I have a hosted WG server and imported client config to amneziaVPN client. It works fine, but split tunneling is not available at all. **To Reproduce** Steps to reproduce the behavior: 1. Open AmneziaVPN client 2. Click on '+' button 3. Click 'File with connection settings' to import your WG config file 4. Select config file for import and enable WG obfuscation 5. Click 'Split tunneling enabled' button on the 'Connect' screen with the newly imported config 6. Check that 'Split tunneling on the server' has status 'Enabled' 7. Click 'Site-based split tunneling' **Expected behavior** Toggle switch is available and hostname/IPs can be added to the list **Actual behavior** Toggle switch is grey, warning pop-ups "default server does not support split tunneling function" **Screenshots** <img width="492" alt="image" src="https://github.com/user-attachments/assets/ef26fdad-30f1-4119-ad86-95a055020f7e" /> **Desktop (please complete the following information):** - OS: macOS Sequoia 15.2 on Apple M4 ** AmneziaVPN client version - 4.8.2.3 **Additional context** AllowedIPs options in the WG client config do not work as well, allowed IPs (other than 0.0.0.0/0) become unreachable and other IPs work but with no tunneling at all

bsakaguchi closed this issue

2026-10-13 20:23:49 +00:00

bsakaguchi commented

2026-10-13 20:23:50 +00:00

Author

Owner

@ulin-evgeny commented on GitHub (Jan 14, 2025):

OS: Ubuntu 22.04, config from Surfshark - same problem.

@ulin-evgeny commented on GitHub (Jan 14, 2025): OS: Ubuntu 22.04, config from Surfshark - same problem.

bsakaguchi commented

2026-10-13 20:23:51 +00:00

Author

Owner

@e-t-l commented on GitHub (Feb 6, 2025):

Windows client, same issue. What is it about the "default server" that would prevent domain-based split-tunneling? Especially since app-based split tunneling works fine, I would have expected the client to be able to split-tunnel out traffic per domain...

@e-t-l commented on GitHub (Feb 6, 2025): Windows client, same issue. What is it about the "default server" that would prevent domain-based split-tunneling? Especially since app-based split tunneling works fine, I would have expected the client to be able to split-tunnel out traffic per domain...

bsakaguchi commented

2026-10-13 20:23:51 +00:00

Author

Owner

@e-t-l commented on GitHub (Feb 6, 2025):

(Also, under split tunneling settings, it says "Split tunneling on the server: Enabled / Can't be disabled for the current server." Why the heck not?? What part of the server configuration dictates this? I'm using a wireguard.conf file generated by ProtonVPN fyi)

@e-t-l commented on GitHub (Feb 6, 2025): (Also, under split tunneling settings, it says "Split tunneling on the server: Enabled / Can't be disabled for the current server." Why the heck not?? What part of the server configuration dictates this? I'm using a wireguard.conf file generated by ProtonVPN fyi)

bsakaguchi commented

2026-10-13 20:23:51 +00:00

Author

Owner

@Nethius commented on GitHub (Feb 18, 2025):

Thank you for your report. Please note that GitHub is not a support channel. For assistance, please contact our support team via chat at https://t.me/amnezia_support_bot or via email at support@amnezia.org.

Our team will review the details and help resolve the issue.

@Nethius commented on GitHub (Feb 18, 2025): Thank you for your report. Please note that GitHub is not a support channel. For assistance, please contact our support team via chat at https://t.me/amnezia_support_bot or via email at [support@amnezia.org](mailto:support@amnezia.org). Our team will review the details and help resolve the issue.

bsakaguchi commented

2026-10-13 20:23:51 +00:00

Author

Owner

@Arahort commented on GitHub (Feb 13, 2026):

My own server which I created manually, without Docker, has the same problem :( Has anyone been able to solve it?

@Arahort commented on GitHub (Feb 13, 2026): My own server which I created manually, without Docker, has the same problem :( Has anyone been able to solve it?

bsakaguchi referenced this issue

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

[PR #542] [MERGED] Update amneziavpn_ru.ts #1901