Expected Behaviour:
Running pi-hole and Unbound, both on a Raspberry Pi Zero 2. The second one I setup has been operating smoothly and as expected, the first has occasionally had NTP errors, and accepts nearly no traffic compared to the second. The second instance shows the client as encrypted via TLS/SSL, while the first indicates it is not. I'm not experienced enough to know what exactly is wrong, but the disparities would seem to indicate to me that there is something broken here .
There is a chance I messed up something with the problematic instance, I had issues with SSH during setup due to having next to no idea what I was doing. Tried to connect from the Pi to my Windows machine, which no longer had a password after the "windows hello" removed it. I do not remember what I tried to do with that to make it fix, as I gave up halfway through. I have since purged and reinstalled OpenSSH.
I have followed the Unbound config setup outlined in Pi-Hole documentation, and both instances are able to resolve DNS queries.
Actual Behaviour:
FTL Dashboard/Client to be end-to-end encrypted, not to have NTP errors, load to be distributed more evenly between instances.
Debug Token:
The problematic instance: https://tricorder.pi-hole.net/DofYIypV/
The functional instance: https://tricorder.pi-hole.net/M67kzkxA/