Web Server and Zenarmor

Started by Rockyuk, October 02, 2026, 10:44:46 PM

Previous topic - Next topic
Hello Everyone,
I have a web server on my home network which runs perfectly. One of my domains expired awhile ago and I re-registered it recently. I also whitelisted/excluded it from within the policy. However it is still being blocked and seen as a deadsite. It is pointing to my server and I can access but it is showing a different IP when I try to install an SSL Certificate.

That's when I noticed it was still being blocked via Zenarmor. My other websites work fine it's just this new one. Any ideas on how I can resolve this please?

Thanks

Did you try to restart ZA engine after whitelisting it?

Regards,
S.
Networking is love. You may hate it, but in the end, you always come back to it.

OPNSense HW
N355 - i226-V | AQC113C | 16G | 500G - PROD

PRXMX
N5105 - i226-V | 2x8G | 512G - NODE #1
N100 - i226-V | 16G | 1T - NODE #2

I would suggest restarting ZA first if you haven't done that after you whitelisted IPs and such.

If that doesn't fix the issue, contact ZA customer support. Dead site issues can't be fixed by yourself (it is caused by low average visitor amounts), so you have to contact ZA if that is the case.

Now certificate issue is easy to fix if you are using Let's encrypt. Instead of running acme client on opnsense, change the public DNS records on the registrar (or whichever hosts them) and run Acme client on the server, where website is hosted on (Let's encrypt tool on opnsense can issue certificates only to domains, which are hosted on servers using same public IP as opnsense is. Let's encrypt uses acme and without manual input, acme client needs to be ran from server or any device using same Public IP. It checks the public DNS records, not local ones)