# Certbot failing and claiming a firewall issue

**URL:** <https://community.letsencrypt.org/t/certbot-failing-and-claiming-a-firewall-issue/206511>\
**Category:** Help\
**Created:** [October 11, 2023, 11:10pm UTC](https://community.letsencrypt.org/t/certbot-failing-and-claiming-a-firewall-issue/206511 "2023-10-11T23:10:19Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![MikeMcQ](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mikemcq/32/52772_2.png) [@MikeMcQ](https://community.letsencrypt.org/u/MikeMcQ)\
**Post date:** [October 12, 2023, 3:47am UTC](https://community.letsencrypt.org/t/certbot-failing-and-claiming-a-firewall-issue/206511/12 "2023-10-12T03:47:57Z")

</div>

Glad at least 443 is working now. It was not open earlier when I only saw port 22.

Yes, your local network test was not reaching your Apache and was being rejected by whatever `micro_httpd` is. Maybe something like a router admin interface?

> [@bdoss](#):
>
> ```nohighlight
> < HTTP/1.1 401 Unauthorized
> < Server: micro_httpd
> 
> ```

Without port 80 you have either DNS Challenge or TLS-ALPN which uses port 443 only.

Apache supports TLS-ALPN with the mod\_md feature. It's quite easy to use. See more details below and then of course the Apache docs. I did one as a test a few months back and had it working inside like 10 minutes and that included reading mod\_md docs.

I don't have time anymore tonite to post more but it is worth a look. Probably easier than automating a DNS Challenge.

> [@Certbot -renew -apache failed](https://community.letsencrypt.org/t/certbot-renew-apache-failed/197596/15):
>
> …

---

_[View the full topic](https://community.letsencrypt.org/t/certbot-failing-and-claiming-a-firewall-issue/206511)._