Miha Kralj
Miha Kralj
You have a stale/expired X1, X2 or R3 CA in your System/Trust/Authorities store. Delete them all and re-import from the site: https://letsencrypt.org/certificates/ 
Uh, bummer... The version in ports is old, old, old development version. The latest version published [here ](https://github.com/nextdns/nextdns/releases) is 1.32.1 - with way more features...
The latest CLI version has a self-update command line option. The old one in ports doesn't. If you would delegate an option to maintain updates of selected non-ports binaries in...
Have code? Yes. Is it clean and publishable? Nooooooo. Let me work on it a bit more.
yes there is... /usr/local/etc/nextdns.conf is the file where nextdns stores all settings. See: `https://github.com/nextdns/nextdns/wiki/Configuration-File-Format` You can manually force it with `sudo nextdns config set -config-file /usr/local/etc/nextdns.conf`
setting id via CLI: `sudo nextdns config set -config `
all nextdns config set parameters: ``` -auto-activate Run activate at startup and deactivate on exit. -bogus-priv Bogus private reverse lookups. All reverse lookups for private IP ranges (ie 192.168.x.x, etc.)...
I am trying to write a javascript code in statements within .volt view to reach out to my.nextdns.com and grab the attributes there. And no matter what method I use,...
Yeah, I know... As all settings for nextdns are api-accessible (all gets and sets) - I thought to bring them all together into a single user interface. And it is...
It looks like the ports version is now up-to-date and we won't need binary in the plugin. 😊