Issues with wireguard on a slate 7

Hello,

I’ve just purchased a slate 7 and i’m finding it impossible to connect to my home router, which is servicing multiple other clients without any issue. I’ve tried downloading the peer configuration to another device and it works fine. Once i try to enable the vpn on the slate screen, it get stuck on connecting. The slate can ping the vpn endpoint without any issue.

Firmware on the slate is the latest one (4.8.3) and the time is accurate.

Is there any trick i’m missing?

Here is what the vpn log shows

Tue Mar 17 09:40:38 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Tue Mar 17 10:37:53 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Tue Mar 17 10:37:54 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:37:54 2026 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.wgclient1, will retry
Tue Mar 17 10:37:54 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:38:26 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:38:28 2026 daemon.notice netifd: wgclient1 (5843): udp      17 59 src=192.168.8.131 dst=192.168.8.1 sport=58537 dport=53 packets=1 bytes=54 src=192.168.8.1 dst=192.168.8.131 sport=53 dport=58537 packets=1 bytes=54 mark=32768 use=1
Tue Mar 17 10:38:29 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Tue Mar 17 10:38:29 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Tue Mar 17 10:54:03 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Tue Mar 17 10:54:04 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:54:04 2026 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.wgclient1, will retry
Tue Mar 17 10:54:04 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:54:22 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:54:25 2026 daemon.notice netifd: Interface 'wgclient1' is now down
Tue Mar 17 10:54:25 2026 user.notice firewall: Reloading firewall due to ifdown of wgclient1 ()
Tue Mar 17 10:58:54 2026 daemon.notice netifd: Interface 'wgclient1' is setting up now
Tue Mar 17 10:58:55 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names
Tue Mar 17 10:58:55 2026 daemon.warn dnsmasq[1]: no servers found in /tmp/resolv.conf.d/resolv.conf.wgclient1, will retry
Tue Mar 17 10:58:55 2026 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.wgclient1 - 4 names

I forgot to post the peer configuration, here it is with the personal data scrubbed out

[Interface]
Address = 198.18.7.7/32
ListenPort = 51820
PrivateKey = slate7privatekey
DNS = 1.1.1.1
MTU = 1420

[Peer]
AllowedIPs = 0.0.0.0/0, ::/0
Endpoint = myrouterfqdn:51820
PersistentKeepalive = 25
PublicKey = myrouterpublickey

Is that interface ip address correct?

I've only ever used unique .conf files for each device, so the idea that you have one that you are using for many is new to me.

I posted the wireguard client configuration, not the wireguard server conf. The IP is the one allocated for this specific client, i’m using fixed addressing in wireguard to make it easier to track bandwidth usage.

Hi

That’s a bit unusual—the configuration looks normal.

Could you follow the guide below to connect the device to GoodCloud and share it with us for remote inspection?

Please also send us the device’s MAC address and the admin panel password via private message so we can access it.

Hello @will.qiu, I haven’t got the slate with me now, I will share the requested data once I have access to it.

No problem on our end—just let us know when you’re available again or when the device is accessible.

@will.qiu I forgot to check if I ever restarted the wireguard service after adding the peer :melting_face: . After a service restart, the session went up instantly. Sorry for bothering you :slight_smile:

1 Like

Glad to hear the issue has been resolved!