rethink-app icon indicating copy to clipboard operation
rethink-app copied to clipboard

Cannot add wireguard as proxy

Open jmakov opened this issue 1 year ago • 5 comments

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

jmakov avatar Feb 08 '25 20:02 jmakov

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.

CapSel avatar Feb 09 '25 00:02 CapSel

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).

ignoramous avatar Feb 09 '25 16:02 ignoramous

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

jmakov avatar Feb 09 '25 20:02 jmakov

+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 avatar Feb 10 '25 21:02 Mywk

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.

Mywk avatar Feb 10 '25 21:02 Mywk