Cannot Configure ID
Context
- CLI Version: 1.37.5
- Platform: Artix Linux
NOTE: My OS dose not use systemd and runs on OpenRC. The daemon client I use are both NetworkManager
and dhcpcd
I went through all the steps of installation, downloading through the AUR with yay
helper and yet I still have a slew of problems I have to deal with. Though the installation went smoothly I cannot configure my ID despite signing in and saving my settings on the nextdns website.
Although it is running as when I input nextdns status
the response is running
and the website tells me:
This device is using NextDNS with another configuration.
I still cannot configure my ID.
When I input nextdns config [ID]
I get:
Error: usage:
When I input nextdns start
I get:
Error: rc-service nextdns start: exit status 1: nextdns | * nextdns: superuser access required
I assume the superuser access would be enabled once i configure my ID
When I input nextdns run
I get:
ERROR: 11:47:17 Cannot start control server: listen unix /var/run/nextdns.sock: bind: address already in use INFO: 11:47:17 Starting NextDNS 1.37.5/linux on localhost:53 INFO: 11:47:17 Listening on TCP/[::1]:53 INFO: 11:47:17 Listening on TCP/127.0.0.1:53 INFO: 11:47:17 Listening on UDP/127.0.0.1:53 INFO: 11:47:17 Listening on UDP/[::1]:53 ERROR: 11:47:17 Startup failed: proxy: tcp: listen tcp [::1]:53: bind: permission denied Error: proxy: tcp: listen tcp [::1]:53: bind: permission denied
So naturally I assumed that because port 53 was tied up I would need to delete whatever daemon was occupying the spot and so I deleted it. When I input sudo lsof -i :53
it tells me that all devices use a nextdns PID
After all of that I still have the same problems described above... S O S
1 reply
-
I'm having a similar trouble on Arch Linux, however the error is
Startup failed: proxy: udp: listen udp: lookup localhost on 45.90.28.39:53: no such host
I ended up configuring systemd-resolved.service because at least it seems to encrypt DNS queries:
Bus client set DNS server list to: 45.90.28.39, 45.90.30.39, fe80::f654:20ff:fe06:a22a, 2a07:a8c0::9c:99bc, 2a07:a8c1:>
still waiting for an answer by the NextDNS team
Content aside
- 2 yrs agoLast active
- 1Replies
- 246Views
-
2
Following