Wireguard Client Unable to connect

I have used a Opal 1200 as my Wireguard server, for the client i’ve used a Puli x300 as on a slate plus 1300 but my client is not connecting.

I have done the port forwarding on the home router, i have got it working with a wireguard client on my android phone but this is the first time i am setting up a client on another device

I have copied and pasted the logs from the slat plus 1300, can anyone help

“Thu Mar 30 08:59:54 2023 daemon.notice netifd: Interface ‘wgclient’ is now down\nThu Mar 30 08:59:54 2023 daemon.notice netifd: Interface ‘wgclient’ is setting up now\nThu Mar 30 08:59:55 2023 user.notice mwan3[20803]: Execute ifdown event on interface wgclient (unknown)\nThu Mar 30 08:59:56 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()\nThu Mar 30 09:00:00 2023 kern.info kernel: [ 320.737604] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT\nThu Mar 30 09:00:00 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nThu Mar 30 09:00:05 2023 kern.info kernel: [ 325.767662] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT\nThu Mar 30 09:00:05 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nThu Mar 30 09:00:08 2023 daemon.notice netifd: Interface ‘wgclient’ is now down\nThu Mar 30 09:00:09 2023 user.notice mwan3[22269]: Execute ifdown event on interface wgclient (unknown)\nThu Mar 30 09:00:10 2023 user.notice firewall: Reloading firewall due to ifdown of wgclient ()\nThu Mar 30 09:00:18 2023 daemon.notice netifd: Interface ‘wgclient’ is setting up now\nThu Mar 30 09:00:24 2023 kern.info kernel: [ 344.806487] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT\nThu Mar 30 09:00:24 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nThu Mar 30 09:00:30 2023 kern.info kernel: [ 350.566314] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT\nThu Mar 30 09:00:30 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nThu Mar 30 09:00:35 2023 kern.info kernel: [ 356.324635] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT\nThu Mar 30 09:00:35 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\nThu Mar 30 09:00:41 2023 kern.info kernel: [ 361.469058] wireguard: wireguard-hotplug IFNAME=wgclient ACTION=REKEY-TIMEOUT\nThu Mar 30 09:00:41 2023 user.notice wireguard-debug: USER=root ifname=wgclient ACTION=REKEY-TIMEOUT SHLVL=1 HOME=/ HOTPLUG_TYPE=wireguard LOGNAME=root DEVICENAME= TERM=linux SUBSYSTEM=wireguard PATH=/usr/sbin:/usr/bin:/sbin:/bin PWD=/\n”

What version of firmware do you have? Have you tried the latest 4.2.1 BETA?