Based on the GoodCloud logs, the device appears to lost internet connectivity, but no Ethernet or Wi-Fi link-down events were recorded. This indicates the local network connection remained up, and the issue is most likely originating from the ISP modem or an upstream ISP outage.
1 Like
Hello, I love using the GL solutions although I have been experiencing some issues related to the thread above.
My VPN this month has stopped working several times via the Wireguard client. Below I attached a log file.
Fri Jan 16 12:53:04 2026 daemon.notice netifd: Interface 'wgclient1' is now up
Fri Jan 16 12:53:04 2026 daemon.notice netifd: Network device 'wgclient1' link is up
Fri Jan 16 12:53:04 2026 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)
Fri Jan 16 12:53:47 2026 daemon.notice netifd: Network device 'wgclient1' link is down
Fri Jan 16 12:53:47 2026 daemon.info dnsmasq[2199]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Fri Jan 16 12:53:48 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Fri Jan 16 12:53:48 2026 daemon.notice netifd: wgclient1 (1729): udp 17 59 src=192.168.2.11 dst=192.168.2.1 sport=40202 dport=53 packets=1 bytes=91 src=192.168.2.1 dst=192.168.2.11 sport=53 dport=40202 packets=1 bytes=396 mark=0 use=1
Fri Jan 16 12:53:48 2026 daemon.notice netifd: wgclient1 (1729): udp 17 59 src=192.168.2.11 dst=192.168.2.1 sport=53189 dport=53 packets=1 bytes=65 src=192.168.2.1 dst=192.168.2.11 sport=53 dport=53189 packets=1 bytes=256 mark=0 use=1
Fri Jan 16 12:53:48 2026 daemon.notice netifd: wgclient1 (1729): udp 17 59 src=192.168.8.239 dst=192.168.8.1 sport=52493 dport=53 packets=1 bytes=91 src=192.168.8.1 dst=192.168.8.239 sport=53 dport=52493 packets=1 bytes=396 mark=32768 use=1
Fri Jan 16 12:53:48 2026 daemon.notice netifd: wgclient1 (1729): udp 17 59 src=192.168.8.239 dst=192.168.8.1 sport=51219 dport=53 packets=1 bytes=65 src=192.168.8.1 dst=192.168.8.239 sport=53 dport=51219 packets=1 bytes=200 mark=32768 use=1
Fri Jan 16 12:53:49 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Fri Jan 16 13:10:32 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Fri Jan 16 13:10:33 2026 daemon.info dnsmasq[13813]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Fri Jan 16 13:10:33 2026 daemon.info dnsmasq[13814]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Fri Jan 16 13:10:33 2026 daemon.info dnsmasq[13814]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Fri Jan 16 13:10:39 2026 daemon.info dnsmasq[13814]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Fri Jan 16 13:10:39 2026 daemon.info dnsmasq[13814]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Fri Jan 16 13:10:39 2026 daemon.notice netifd: Interface 'wgclient1' is now up
Fri Jan 16 13:10:39 2026 daemon.notice netifd: Network device 'wgclient1' link is up
Fri Jan 16 13:10:40 2026 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)
Fri Jan 16 13:10:33 2026 daemon.info dnsmasq[13814]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Fri Jan 16 13:10:39 2026 daemon.info dnsmasq[13814]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Fri Jan 16 13:10:39 2026 daemon.info dnsmasq[13814]: reading /tmp/resolv.conf.d/resolv.conf.wgclient1
Fri Jan 16 13:10:39 2026 daemon.notice netifd: Interface 'wgclient1' is now up
Fri Jan 16 13:10:39 2026 daemon.notice netifd: Network device 'wgclient1' link is up
Fri Jan 16 13:10:40 2026 user.notice firewall: Reloading firewall due to ifup of wgclient1 (wgclient1)
Most likely an issue on the server's side or with the connection in general.
What does the log on the server tell you?
So I thought maybe it was an issue with my connection but then I logged into my surfshark account and used them as my VPN client and issue persists. Should I include the log while I use that client?
Do you have access to the server side logs? If not, can you have someone in your server’s location configure GoodCloud?
I do not but I can look into getting those and configuring Goodcloud. By the way, my server is set up as a “bridge” Is this recommended or would it cause issues?
From what I understand using your home router in bridge mode is one of the suggested configurations. I personally don't do this and use port forwarding, which works fine for me.
I'd recommend checking the server side logs for the issue you're having. For me, they revealed that the disconnections were coming from the upstream ISP so there isn't much that can be done.
The reason it's a good idea to set up GoodCloud is that it will give you access to your server’s logs and terminal without having to be physically near it
When using Surfshark, is the router also unable to establish a connection?
To help us isolate whether the issue is with the network environment or the router configuration, please test the following:
- Phone Comparison: Connect your smartphone to the same network as the router. Attempt to connect using the Surfshark app or your home VPN profile on the phone. Does it connect successfully?
- Remote Inspection: If the phone connects but the router does not, please share your router with us via GoodCloud so we can perform a remote inspection. You can find the tutorial here: Technical Support via GoodCloud
After enabling access and sharing it, please send us your MAC address and Admin Panel password via private message only so we can access the device securely.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.