Wireguard error on Nethsecurity 8.7.1

NethSecurity
,
1

Hi everyone, I’d like to configure WireGuard VPN on a device I just updated to version 8.7.1, but I’m getting this error:
Unable to get setup parameters
There was an error retrieving the data to add the WireGuard server. Please try again later.
OpenVPN RoadWarrior server is working properly.
A possible problem while upgrading from a previous version?

This is a 6-port firewall device with an Intel N150 processor, purchased online.
Thanks for any suggestions.

error
error592×351 15.1 KB

2

Hi Luca,

you may try a hard refresh of the browser or another browser to exclude browser/cache issues.

Are there errors in the logs?

You could try if it works on command line, see also ns-api | NethSecurity

3

Hi Markus, I’ve tried different browsers but I get the same error. I tried the command: api-cli ns.wireguard get-instance-defaults
but I get the error: HTTP Error 401: Unauthorized
I don’t see any errors in the logs.

4

Please try following command:

/usr/libexec/rpcd/ns.wireguard call get-instance-defaults

Let’s check existing wg servers:

/usr/libexec/rpcd/ns.wireguard call list-servers
5

Here are the results of the suggested commands:

root@NethSecBellei:~# /usr/libexec/rpcd/ns.wireguard call get-instance-defaults
/usr/bin/dig: couldn’t get address for ‘resolver1.opendns.com’: not found
{“listen_port”: 51820, “instance”: “wg1”, “network”: “10.160.180.0/24”, “public_endpoint”: “”}
root@NethSecBellei:~# /usr/libexec/rpcd/ns.wireguard call list-servers
{“instances”: }

6

Did you setup that server as DNS server?

Does the following work on command line?

dig resolver1.opendns.com
7

I don’t think I set Nethsecurity as DNS, I set public DNS as forwarder. If I run the dig I get:

root@NethSecBellei:~# dig resolver1.opendns.com

; <<>> DiG 9.20.11 <<>> resolver1.opendns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14213
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;resolver1.opendns.com. IN A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Tue Nov 25 16:23:00 CET 2025
;; MSG SIZE rcvd: 50

8

i can see this:

root@NethSecBellei:~# cat /etc/resolv.conf
search lan
nameserver 127.0.0.1
nameserver ::1

9

Your NethSecurity can’t resolve resolver1.opendns.com.

Here’s a working dig command:

root@keepout:~# dig resolver1.opendns.com

; <<>> DiG 9.20.11 <<>> resolver1.opendns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14545
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;resolver1.opendns.com.		IN	A

;; ANSWER SECTION:
resolver1.opendns.com.	147	IN	A	208.67.222.222

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Tue Nov 25 16:28:16 CET 2025
;; MSG SIZE  rcvd: 66

That’s ok.

Maybe you could try another public DNS like 8.8.8.8 or 1.1.1.1.

Does it work to ping a server?

ping community.nethserver.org
10

Thanks Markus! I changed the resolv.conf file to add DNS 8.8.8.8, and now the device correctly installs the new Wireguard instance.
Thanks for the support!!!

1 Like
11

You’re welcome.
The resolv.conf was correct, I think you just need to use a correct DNS forwarder, see DNS & DHCP — NethSecurity documentation

1 Like
12

Thanks Markus, actually when I wrote that I had set public DNS, I actually meant 8.8.8.8 and 1.1.1.1. Despite that, I didn’t understand the problem, which was then solved by changing the resolv.conf.
Thanks again for the support, everything is working fine now!

1 Like
13

This still shouldn’t happen, filled a bug entry for it:

Thank you!

2 Likes