Messages

I don't have an answer to your question. On further inspection of my CA authority after applying the patch, I noticed that the private key was corrupted.  I went back to my backup configuration files of a year ago, the private key was already corrupted.  I went further back to 2 years ago, mysteriously, the cert part was corrupted while the private key was apparently intact. I pasted the private key of that configuration file to my current private key section and saved it. There was no error reported, maybe implying the private key is compatible with the cert of the CA authority. I am not knowledgeable enough to explain what happened. 

Thanks a lot, Franco.  The patch worked to enable viewing of the "Authorities" and "Certificates" pages. I am not sure about the possibly broken CA data. Everything related to my ACME certificates appeared to work perfectly.

There is no response as to how to fix this problem.  I have two machines, one under proxmox and one bare-metal. Both had same issues after upgrading from 25.1 to 25.7.  Just wonder whether most people didn't experience this issue.

I have the same issue: error viewing system/trust/authority | certificates.  I tried creating a new internal CA and it didn't show up in the authority's page. However, in the filter selection in the certificates page, I can see the name of my newly created CA. The existing certificates in my Opnsense server appeared to be still functioning properly.

Updated to 24.7.10_2 and the NAT reflection behavior returns to what is expected.  Not sure what caused the first observed problem with 24.7.10_1.  Anyway, problem is gone.

Some webservers are not accessible inside LAN but accessible from the internet after the update.  Reverting to 24.7.9_1 solved the problem.

I didn't have this WAN_DHCP6 gateway offline problem after update to 24.7.3_1 but it occured after updated to 24.7.4  I tried you trick of check/uncheck the "Disable Host Route" option and didn't solve the problem.  I also tried restarting the cable modem without solving the problem. So far, it appears that no one else is seeing this problem.

Edit:
After reconfiguring WAN interface, DHCPv6, the problem went away.   Looks like the problem was due to misconfiguration.

This is the error message when NetData was running on 23.1.2: "apps.plugin   pid 1433 netdata states parent 1, but the later does not exist." The error message appeared persistently.

After update to 23.1.2, NetData CPU usage jump to ~200% as shown in top. Opnsense is running in a Hyper-V VM. The host overall CPU usage jumped from ~12% to persistently over 50%.  After uninstalling NetData, CPU usage was back to normal.

I have similar problems and the logs looked similar too.  The ethernet detachment of both WAN and LAN occurred around the same time.  I was wondering whether it was due to the driver for my I225v3 NIC (2.5G NIC). However, it looks like the problem occurs with igb# NIC too.  Some previous posts about similar problems mentioned associations with MAC address spoofing, IPS mode which are present in my case.  There could be other possibilities apart from NIC hardware problem. Recently, Suricata logged a lot of "ET DOS Possible NTP DDoS Inbound Frequent Un-Authed MON" attacks and the ethernet detachment incidences appeared to occur sometime after these attacks. Wonder if that could be a trigger for the ethernet detachment incidence.

Mine frequently renews the wan ip address, which didn't change, and caused unbound to restart.

Same issues here.  After uninstalling HAProxy, ACME and certs appeared again as before upgrade.

Turn-out MS Edge Browser also worked after deleting the cookie for my opnsense server.  Just not sure why it affected only the "log file" of Unbound.  I can view other system log files without problem.

Thanks for the info. 

I was using MS Edge browser and got non-responding page on the "log files" tab.  I changed to Chrome browser and it worked.  It could be a browser problem or a cache problem.  I would clear the Edge browser cache and try again.

 # ls -lah /var/log/resolver.log
ls: /var/log/resolver.log: No such file or directory