Been in Brasil for months, wireguard worked completely fine with the setup in the image.
Have moved to another city to a friends house, plugged in the slate via the same setup as in previous city, wireguard no longer working. Need to resolve this by Sunday ideally, can anybody help?
logs below:
"Sat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Zone 'lan'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Zone 'wan'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Zone 'guest'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Zone 'wgclient'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Set tcp_ecn to off\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Set tcp_syncookies to on\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Set tcp_window_scaling to on\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Running script '/etc/firewall.nat6'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Running script '/etc/firewall.swap_wan_in_conn_mark.sh'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Running script '/var/etc/gls2s.include'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): ! Skipping due to path error: No such file or directory\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Running script '/usr/bin/gl_block.sh'\nSat Dec 7 00:24:26 2024 daemon.notice netifd: wgclient (20553): * Running script '/etc/firewall.vpn_server_policy.sh'\nSat Dec 7 00:24:27 2024 daemon.notice netifd: wgclient (20553): Failed to parse json data: unexpected character\nSat Dec 7 00:24:27 2024 daemon.notice netifd: wgclient (20553): uci: Entry not found\nSat Dec 7 00:24:27 2024 daemon.notice netifd: wgclient (20553): cat: can't open '/tmp/run/wg_resolved_ip': No such file or directory\nSat Dec 7 00:24:27 2024 daemon.notice netifd: Interface 'wgclient' is now down\nSat Dec 7 00:24:27 2024 daemon.notice netifd: Interface 'wgclient' is setting up now\nSat Dec 7 00:24:27 2024 daemon.notice netifd: wgclient (20647): Name does not resolve: `zr6353d.glddns.com:51820'\nSat Dec 7 00:24:27 2024 daemon.notice netifd: wgclient (20647): Configuration parsing error\n"
Sorry for this issue, please restart the DDNS service on the VPN server side, many users have verified that this method resolves the DDNS issue. If this doesn’t work, please send me your DDNS domain via private message.
If you need a temporary workaround, please manually modify the Endpoint in your VPN client configuration to your public IP address. For example: change Endpoint = xxxxxx.glddns.com:51820 to 1234567:51820. However, please note that this solution may not work for dynamic public IP addresses.
This will not help you now, but on my remote GL iNet routers, I have my routers reboot daily using cron, as it clears these types of issues if they ever occur. I have been traveling for years now, and it keeps things working.
I am having the same problem, had wireguard working for weeks and yesterday it stopped working, I have restart the wireguard server router and still have no way to connect, what can I do?
Rebooting restarts all processes, and can clear things like network issues and memory leaks. I do it on my GL iNet routers that run remotely and have been doing it for years.
Many peoples may tell you it's not necessary, but I find it keeps my routers working.
It worked, however for some reason the time zone is not showing as UK any more. When I plug Ethernet into my mac, it used to switch to the uk VPN time zone immediately which it doesn’t do now. The client router time zone is set to London/Europe. How do I fix this?
Great tip. I will need to get someone in England to login to the admin panel and set up the daily reboots. Is there a way of accessing the server admin panel remotely?
By using GoodCloud. If your device isn't added to GoodCloud so far, the person who needs to enter the admin panel (physically on the remote area) should enable it as well.
Or you might try to get the current WAN IP (maybe you have some other systems at this location which might log the IP somehow?) and connect via WireGuard then, using IP instead of DDNS for this time.