Manual certonly fails http-01 challenge

[inti]

Running certonly and manual since renew was failing and I wanted to make sure webserver config was not an issue. CA cannot access the acme-challenge file, though it is present and being served by webserver. I'm stumped.

My domain is:

tiles.resi.solutions

I ran this command:

sudo certbot certonly --manual -v

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Please enter the domain name(s) you would like on your certificate (comma and/or
space separated) (Enter 'c' to cancel): tiles.resi.solutions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
An RSA certificate named tiles.resi.solutions already exists. Do you want to
update its key type to ECDSA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(U)pdate key type/(K)eep existing key type: k
Certificate is due for renewal, auto-renewing...
Renewing an existing certificate for tiles.resi.solutions
Performing the following challenges:
http-01 challenge for tiles.resi.solutions

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Create a file containing just this data:

IRQoIAlrOy6j3XZ50XWq6WRE4akI9JNldiHpGaepjKE.ME9iEyfO2ehgbcP6XugRdQWArNqHrHQFnnCLTejUfsI

And make it available on your web server at this URL:

http://tiles.resi.solutions/.well-known/acme-challenge/IRQoIAlrOy6j3XZ50XWq6WRE4akI9JNldiHpGaepjKE

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue
Waiting for verification...
Challenge failed for domain tiles.resi.solutions
http-01 challenge for tiles.resi.solutions

Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
  Domain: tiles.resi.solutions
  Type:   connection
  Detail: 67.164.149.52: Fetching http://tiles.resi.solutions/.well-known/acme-challenge/IRQoIAlrOy6j3XZ50XWq6WRE4akI9JNldiHpGaepjKE: Timeout after connect (your server may be slow or overloaded)

Hint: The Certificate Authority failed to verify the manually created challenge files. Ensure that you created these in the correct location.

Cleaning up challenges
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):

apache 2.4.52

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

Ubuntu 22.04 LTS

My hosting provider, if applicable, is:

self-hosted

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 2.7.2

[Osiris]

Something is wrong with your webserver in general: it accepts connections on HTTP port 80, but after that it doesn't do anything any more. This includes both the challenge file and your website in general: it's simply not working.

Please fix your website so it works properly on port 80 first before continuing with trying to get a certificate.

By the way: why did you choose the --manual plugin? And not e.g. the --webroot plugin?

Funnily enough it does actually respond using HTTPS on port 443. Not sure why that is though.

[inti]

You're right, thank you. An issue with port forwarding from the router. Sorry to trouble everyone!

I'll look into --webroot, thanks.