search

NHAS / wag

Simple Wireguard 2FA
BSD 3-Clause "New" or "Revised" License
486 stars 27 forks source link

connection issues with MS Edge browser, Firefox OK #82

Closed uplight-dev closed 7 months ago

uplight-dev commented 7 months ago

I've been getting constantly, every few minutes or so, this client-side log:

2023-12-21 23:03:59.082: [TUN] [...] Keypair 1 destroyed for peer 1

After this, the session gets destroyed and I need to relogin with hardware key. Since WAG is wrapping wireguard itself, I've no idea how to run commands like wg on server to show/investigate the connectivity issues.

Is there a way to investigate still?

Thanks!

NHAS commented 7 months ago

Hm, I havent seen that on my deployments unfortunately. If you're using the docker container version of wag you can jump in with docker exec -it <container> /bin/bash and have a look,

Otherwise you may need to install the wg-tools on a base metal install.

Not really sure how to help you as each deployment is quite different and it might be devices in the way of wag and the internet.

uplight-dev commented 7 months ago

Thanks for trying, no worries!

Actually I'm not sure this is the cause, but I was using MS Edge browser to login to WAG. Since I passed to Firefox I didn't encounter the issue ... yet.

Can the browser cause the client to be kicked-out of WAG and have to relogin?

Also, with wg-tools you meant to try using wireguard standalone, without WAG, is that it? Or can I use it in collaboration with WAG?

uplight-dev commented 7 months ago

Do you know if the session is maintained client-side or server-side? I tried to clear cookies but it keeps me logged-in. So I'm not sure which session-mechanism is being used.

NHAS commented 7 months ago

Can the browser cause the client to be kicked-out of WAG and have to relogin?

In later versions there is a logout url on the bottom of the page. But in earlier versions no, you could force it by locking/unlocking an account.

Also, with wg-tools you meant to try using wireguard standalone, without WAG, is that it? Or can I use it in collaboration with WAG?

You can use wg-tools in conjunction with wag, its all wireguard so things can still see and interact with the WG device that wag sets up. Just if you change things wag may get unhappy.

Do you know if the session is maintained client-side or server-side?

Its all server side based on your network address and client wg public key.

uplight-dev commented 7 months ago

if it's all server-side, can there be anything at all related to MS Edge that could cause a random connection close? Because with Firefox I didn't see any issues. And I retried MS Edge and again had issues, after 1-2 minutes.

uplight-dev commented 7 months ago

actually it happened in Firefox also, but after about 45 minutes. I'll try with wg-tools and/or a bare wireguard install.