DNSCrypt service did not automatically start after scheduled reboot

[MrHappyHippo]

Hi everyone,

I recently configured a cron job for a scheduled reboot every 3 days on my OPNsense firewall.

After the reboot this morning, I noticed that I had no internet connectivity. The issue turned out to be that the DNSCrypt service did not automatically start after boot. I had to manually start DNSCrypt first and then restart the Unbound service afterward to restore internet access.

My setup is currently:

Destination NAT rule redirecting all DNS traffic to Unbound
Unbound configured with query forwarding to DNSCrypt


I am trying to understand:

Should DNSCrypt normally start automatically after reboot?
Is there additional configuration required to ensure proper startup order?
Could this have been a one-time startup failure?
Where can I find DNSCrypt startup/error logs in OPNsense to troubleshoot this?
Is there a recommended way to ensure Unbound waits for DNSCrypt before starting?

Any suggestions or troubleshooting tips would be appreciated.

Thanks!