Asus router let's encrypt stuck on "Authorizing"

I've set up DDNS with Asus (it shows Active status). I have a public IP address (dynamic IP currently is: ) I have used the Request a cert from Let's Encrypt and a couple days later it still shows as "Authorizing." I'm wondering about next steps to get this working.

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: web ui: WAN / DDNS/ HTTPS/SSL: Free Certificate from Let's Encrypt, select APPLY

It produced this output: Authorizing

My web server is (include version):

The operating system my web server runs on is (include version): Asus RT-86AXU firmware: [

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know): Admin Web UI only

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

@srmccallister , welcome to the community!

I assume you have a home set-up as you are providing firmaware version of the device. It looks like the HTTP port is closed on your router:

tumbleweed:~ # curl -s -v ''
* Host was resolved.
* IPv6: (none)
* IPv4:
*   Trying
* connect to port 80 from port 55632 failed: Connection timed out
* Failed to connect to port 80 after 133351 ms: Couldn't connect to server
* Closing connection
tumbleweed:~ # 

You may want to configure your router opening the HTTP (80) and HTTPS (443) ports and redirect the inbound connections to your ASUS device.


@srmccallister here is a link Asus [Troubleshooting] How to fix opening ASUS Router WEB GUI appears “Your connection is not private” | Official Support | ASUS USA

1 Like

And Ports 80 & 443 are being filtered

$ nmap -Pn -p80,443
Starting Nmap 7.80 ( ) at 2024-03-17 22:28 UTC
Nmap scan report for (
Host is up.
rDNS record for

80/tcp  filtered http
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 3.12 seconds
1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.