Plugin list empty and DDNS not woking

Started by J89eu, September 04, 2023, 11:51:02 AM

Previous topic - Next topic
September 04, 2023, 11:51:02 AM Last Edit: September 04, 2023, 11:56:40 AM by J89eu
Hi all

Had some recent issues with my setup so decided to reset and start again. This kept the plugins which is great but I seem to be having issues with the plugins in general. I believe it's somewhat DNS related but I can't figure out what.

I use AdGuard, running on OpnSense via the plugin with AdGuard using DNS servers of Cloudflare.

I have DNS in System > Settings > General set to my AdGuard IP which is just the IP of OPNSense
I have DNS in Services > DHCPv4 > [LAN] also set to the AdGuard IP which  is just the IP of OPNSense.

This all seems to work for me and I can navigate pages just fine.

Since then I have noticed that my Plugins page doesn't load and the DDNS doesn't seem to update my IP nor report any Current IP or Updated info. This is the DDNS plugin, using Cloudflare, settings verified and believed to be correct. Also the logs are empty.

Unbound is being used but on a different port and mostly just to register DHCP mappings to AdGuard.

So as this seems to have kicked in since the AdGuard DNS setup but what is causing the issues has me a bit lost. Can anyone assist?

Running "pkg update -f" All seems to work:
pkg update -f
Updating OPNsense repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%  235 KiB 240.6kB/s    00:01
Processing entries: 100%
OPNsense repository update completed. 835 packages processed.
Updating mimugmail repository catalogue...
Fetching meta.conf: 100%    163 B   0.2kB/s    00:01
Fetching packagesite.pkg: 100%   58 KiB  59.7kB/s    00:01
Processing entries: 100%
mimugmail repository update completed. 190 packages processed.
All repositories are up to date.


Pinging the pkg server also works:
ping pkg.opnsense.org
PING pkg.opnsense.org (89.149.222.99): 56 data bytes
64 bytes from 89.149.222.99: icmp_seq=0 ttl=56 time=11.947 ms
64 bytes from 89.149.222.99: icmp_seq=1 ttl=56 time=12.785 ms


Set Adguard as primary dns in Services and try again

Quote from: J89eu on September 04, 2023, 11:51:02 AM
I have DNS in System > Settings > General set to my AdGuard IP which is just the IP of OPNSense
I have DNS in Services > DHCPv4 > [LAN] also set to the AdGuard IP which  is just the IP of OPNSense.

You shouldn't need to do either of these things.  As long as you have both of the DNS Options unchecked on the System->Settings->General page it will automatically use the local DNS for internal lookups.  And if you don't set a DNS option in DHCP then it will default to the gateway which should be your OPNSense.