Timeout during connect but files are accessible through browser

[okiyama]

My domain is: www.writeshite.com, writeshite.com

I ran this command: certbot certonly --webroot --dry-run

It produced this output:
PS C:\Windows\system32> certbot certonly --webroot --dry-run
Saving debug log to C:\Certbot\log\letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Please enter in your domain name(s) (comma and/or space separated) (Enter 'c'
to cancel): www.writeshite.com,writeshite.com
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for writeshite.com
http-01 challenge for www.writeshite.com
Input the webroot for writeshite.com: (Enter 'c' to cancel): C:\Users\Julian\IdeaProjects\writing.game\src\main\resources\static

Select the webroot for www.writeshite.com:

---

1: Enter a new webroot
2: C:\Users\Julian\IdeaProjects\writing.game\src\main\resources\static

---

Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 2
Waiting for verification...
e[31mChallenge failed for domain writeshite.come[0m
e[31mChallenge failed for domain www.writeshite.come[0m
http-01 challenge for writeshite.com
http-01 challenge for www.writeshite.com
Cleaning up challenges
e[31mSome challenges have failed.e[0m
e[1m
IMPORTANT NOTES:
e[0m - The following errors were reported by the server:

Domain: writeshite.com
Type: connection
Detail: Fetching
http://writeshite.com/.well-known/acme-challenge/ag-rU-uDRACFuAzG17JUVJdiCDZDIFiQ2ltn5gl8hVI:
Timeout during connect (likely firewall problem)

Domain: www.writeshite.com
Type: connection
Detail: Fetching
http://www.writeshite.com/.well-known/acme-challenge/texoDlP1WSFhdX0XgxTYIqVhqFysv94b5YqsD8OtHYA:
Timeout during connect (likely firewall problem)

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.

My web server is (include version):
tomcat (embedded in spring boot app)

The operating system my web server runs on is (include version):
Windows 10

My hosting provider, if applicable, is:
None, running locally off desktop

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

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

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

I get the timeout error, however I copied the acme-challenge folder and pasted it back after it was deleted, and it's accessible from a browser:
http://writeshite.com/.well-known/acme-challenge/ag-rU-uDRACFuAzG17JUVJdiCDZDIFiQ2ltn5gl8hVI
http://www.writeshite.com/.well-known/acme-challenge/texoDlP1WSFhdX0XgxTYIqVhqFysv94b5YqsD8OtHYA

What could possibly be making this not work?

[Osiris]

@okiyama

and it's accessible from a browser

It might be for your endpoint, but it's not for me.

Did you open port 80 in every firewall? Did you create a NAT portmap to your desktop, if applicable? Does Optimum Online even allow incoming connections to port 80?

[okiyama]

Ahh yep, it's Optimum. They've got an option in my account to enable port 80 that defaults to blocked. I'll need to wait for my wife to finish up her Zoom class since it restarts my modem to enable that, then I'll post here with results.

[okiyama]

That was it, thank you!

For future reference, I went to https://www.optimum.net/internet/boost/ and enabled Port 80 from there:

You can also navigate via the Internet link at the top (after signing in), then there's a link for Port Configuration.

[Osiris]

For HTTPS you also need an open port 443. I don't know if that's opened by default or if you can open that port too.

[okiyama]

Seems Optimum lets that through, no idea why. https://www.writeshite.com looks to all be working as expected (I used 3G to get an external route)! (Though that URL will come up and down since I'm still in development)