Messages

Yeah, the update did the reboot shortly after.  I even rebooted one more time to make sure I wasn't missing something.

I can confirm this.. When I upgraded to the latest patch level it wouldn't start.

checking configctl complained about dnsbl.conf missing.  Then a python module couldn't be opened for read, which was in /var/unbound.

Had to revert back to the previous release to get back up and running

I'm on the latest patch and wireguard appears to be working for me.  However, I'm not using any site to site wireguard VPN tunnels, this is just 'roadwarrior' type stuff.

That's exactly what I use and the exact setup.  I have my host.domain.tld and the associated password generated for that host and that's what I use for username and password, works for me.

Strange.

Are you using HE or HE TunnelBroker ?  Really depends which service you're using and what you're using to check the IP to update to their DNS.

If using dns.he.net to manage DNS, the record must be in place and set as a 'dynamic' record.

What steps have you done so far?

Just as the previous poster said, if you had existing connections and then changed the rules, they won't apply immediately to existing or established connections....

If you need it to apply immediately, reboot the firewall.

When you enable the auth server, the default is <token><Password>

If you want it to be <password><token> you'll have to go into the two factory auth server config and check "Reverse token order"

yes, I know. I want to use it  password+token but as i say i've tested both ways in terms of testing and in the config.  neither make any difference.

Strange, I set it up last night just to test and everything worked for me.

When you enable the auth server, the default is <token><Password>

If you want it to be <password><token> you'll have to go into the two factory auth server config and check "Reverse token order"

This just came up in the IRC channel.. I posted this link I found that appears to have been a PR for this exact thing, however, it doesn't appear that there was any movement on it after Sep, 2021:  https://github.com/opnsense/core/pull/4715

Well, if you mean os-ddclient, the log files should be right there within the same context menu:

Services -> Dynamic DNS ->Log File


Then at the top you can select a severity to view for troubleshooting.

If you read the descriptions of each of those options within the UI, it explains it much better than I. 

Does this help?

https://prnt.sc/26wais9

Did you look under Firewall -> Settings -> Advanced

Make sure that:

Reflection for port forwards   
Reflection for 1:1   
Automatic outbound NAT for Reflection

are all checked, see if that helps (NOTE: You may have to reboot the firewall for these to take affect)

Just tested it and it classified those sites properly for me.

found a script for cloudflare DDNS updater

https://github.com/K0p1-Git/cloudflare-ddns-updater

hope that someone can integrate this as well.

Yeah just saw this myself.  The patch that Ads provided earlier in the thread does allow you to have both in the GUI and usable so you can slowly migrate over.

I'm going to wait for the updated GUI changes before moving over from the legacy plugin as I use he.net for DNS on one of my domains, the underlying ddclient does support it, but the GUI just doesn't have the config.

but alas, it's easy to wait :)