Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot add wireguard as proxy #1863

Open
jmakov opened this issue Feb 8, 2025 · 5 comments
Open

Cannot add wireguard as proxy #1863

jmakov opened this issue Feb 8, 2025 · 5 comments
Assignees

Comments

@jmakov
Copy link

jmakov commented Feb 8, 2025

Scanning the QR code results in "Invalid proxy config" on latest GrapheneOS

@CapSel
Copy link

CapSel commented Feb 9, 2025

I was just trying to add Wireguard proxy and it seems that I had a similar problem caused by DNS, AllowedIPs (network-ending-with-zero/mask), Addresses (ip/mask).

So for example valid:

  • AllowedIPs would be 10.0.0.0/24
  • Addresses would be 10.0.0.2/24
  • DNS for example 1.1.1.1

Except that I have one peer with IP:PORT (like 1.0.0.0:55555).

Try downloading Wireguard application and setting up your connection there - it can be exported there and then imported to Rething. Original app can have more verifications and more verbose messages.

@ignoramous
Copy link
Collaborator

ignoramous commented Feb 9, 2025

I was just trying to add Wireguard proxy and it seems that I had a similar problem caused by DNS, AllowedIPs (network-ending-with-zero/mask), Addresses (ip/mask).

Do these problems also show up in the official WireGuard for Android app? If so, we should fix these (feel free to share a sample config with randomized but proper keys, if needed).

@jmakov
Copy link
Author

jmakov commented Feb 9, 2025

Yes. But for some reason it only happens if I run wg-easy with podman (containers/podman#23686 (comment)). When running with docker I can add it as a proxy and it works.

@Mywk
Copy link

Mywk commented Feb 10, 2025

+1, copying the QR code and manually creating a config with that content results in the exact same behaviour.

Example config that is seen as invalid:

[Interface]
PrivateKey = hidden
Address = 10.0.1.2/32

[Peer]
PublicKey = hidden
PresharedKey = hidden
Endpoint = sever:port
AllowedIPs = 0.0.0.0/0,::/0
PersistentKeepalive = 21

Manually adding the config through the add menu works fine.

@Mywk
Copy link

Mywk commented Feb 10, 2025

Update: Seems related to the private key, after importing a config that reports as invalid, manually copying the private key and saving the configuration seems to make that warning disappear and I'm able to connect fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants