Web UI Not Obtaining Data from Firewall and Other Issues

[Keionys]

Hello everyone. I have been playing around with trying to use Opnsense and get a feel for how it all works. I have a few weird issues. I have tried to reinstall the firewall multiple times to solve these issues and have been looking around online for about a week with no help. So I wanted to come to the forums to see if I could get some help.

First, I am unable to ssh into the system. It will just hang and then the connection will timeout. I can ping my gateway and login to the web client to setup my firewall and network. I can even ssh into other systems on the network.

Which brings me to the second issue. It seems that there is a lot of information that isn't being gathered. I'm not seeing any services listed on the dashboard from the widget. Also, the version is just listed as "-". It looks like:
-
FreeBSD 13.2-RELEASE-p1
OpenSSL 1.1.1u 30 May 2023

When I go to update the software it just sits at the spinning circle under the updater. Without pulling any information. It just does  this forever without getting any updates.

This being said, I am able to setup and configure the firewall. I can make rules and the DHCP is working and giving out addresses. I have internet access across all me devices. I did have to make a few rules to allow DNS to pass from the LAN to the Firewall but other than that most of the settings are default from the configuration wizard.

However, when I want to look at the DHCPv4 leases to see what devices are connected and configure a few static IP addresses, it get the error message: "An API exception occurred" with the error message "/usr/local/opnsense/mvc/app/controllers/OPNsense/DHCPv4/Api/LeasesController.php:110: array_merge(): Argument #1 must be of type array, null given"

Does anyone have any idea why my install is acting outside of the ordinary? Why can't I see the version or run an update? What does this error message mean in my DHCPv4 Leases?

[Keionys]

I'm also curiously unable to login locally on the router itself. With either the root account or the user created as an admin.

There's a lot I don't understand about why these things seem to be not working when they should.