Hi alzhao, sure thing, I will PM you the configs.
Thanks a lot!
Mine has also started doing this recently. Even tried a firmware reset to no avail.
Nevermind, I fixed it. I was previously copying and pasting the config but this time I downloaded the config.
A note to users where the wireguard server is Unraid: Download the config (don’t copy and paste) and upload the zip file into the Slate’s Admin Panel.
1 Like
I love the ‘use QR Code’ feature of the App. No typos, no wrong file format. Just works.
1 Like
Do you observe what format is not correct when doing copy and paste?
It’s a good question but unfortunately I couldn’t tell. I didn’t see any visual difference.
I should note that I was using android, copying from Unraid’s Wireguard VPN manager, and using the “paste as plain text option”. For various reasons, I also had to save into a Bitwarden secure note.
I later remembered how to do attachments in Bitwarden so I just attached the zip of the conf that Unraid provided.
1 Like
This fixes the issue! I uploaded the .conf and it worked
Strangest thing - the what I uploaded vs what I c&p into the field is 100% the same.
Tried it out a few times even to check.
2 Likes
hi, can you send the .conf info ? you clear the encry key, i want to find which is different from my conf.
I have the same issue here. I have tried copy and pasting the config, installing the app and using the QR code, going into VI and editing the config file, etc. I see nothing wrong with the config but I cannot connect to my self host VPN. My VPN is running on untangle but I’m fairly certain the problem is on the mobile router side.
I I have the same issue here too is the problem fixed?
I have a brand new AX1800 4.0.3
the Wireguard server is a mv 1000 with 3.215 both in the same time zone
My wireguard connections work between 2 GL MV 1000
Thanks
I was able to triage mine. It looks like my other WireGuard clients just “work” from within the network and show connected. If I’m in the NAT’d space for my GL.iNet device it doesn’t work.
Looking at the logs of my server (untangle) side it appears that the iOS clients aren’t really connecting when in the NAT’d space but show it as such on the iOS device. I tethered my GL to my phone so I could come in from the external IP and life is good, it’s working.
I have just found the same issue on my AXT1800.
Connection to Wireguard at home (hosted on AX1800) or Mullvad does not show the issue.
I have created a Wireguard connection profile to Cloudflare WARP (Teams) and the issue appears.
Using the same connection profile and connect from a Ubuntu PC, it just works fine.
Maybe kernel related issue?
Please note Cloudflare WARP wireguard config will expire. I don’t know how it works but mine expires next day.
The “REKEY TIMEOUT” message does not differentiate the reasons. So it is kind of difficult to solve easily.
Oh it will expire? Good to know that. I have tried WARP+ last night and it works. I am trying out WARP+ (Teams) to see the difference.
By the way I have flashed Kernel 5.4 but “REKEY” issue still exists.
https://dl.gl-inet.com/?model=axt1800&type=beta
Does v4.1.0 release come with kernel 4.4, and kernel 5.4 is v4.0.3?
It seems to be a bit confusing.
The author said the key should work permanently:
Still 4.4.60
kernel 5.4 is only for testing purpose now. The release will be using 4.4.60
I suggest to clarify the OpenWRT / GL-WRT version and Kenel version on that page.
It looks like the latest version is:
v4.1.0.with kernel 4.4
v4.1.0.with kernel 5.4
But it is:
v4.1.0.with kernel 4.4
v4.0.3.with kernel 5.4
Only the beta you used which we labeld kernel 5.4 is using 5.4.
All other beta and release is using 4.4.60.
Hello,
Having the same trouble with slateax wg client REKEY TIMEOUT, when it worked it was very fast to connect.
I noticed the wg server had a different client port listed on its show for the routers config.
I changed this to match on the slateax and boom, perf connection.
Hope this helps someone. I dont remember specifying the client port originally. although
much trial and errors getting things to work… If it happens again I will try just removing the listen port from slatax config this seems to be dynamic.
Cheers
1 Like