Timeout error when trying to generate certonly with apache2

Please fill out the fields below so we can help you better.

My domain is: fedex.etrade.net.ph

I ran this command: sudo certbot --apache certonly

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log

Which names would you like to activate HTTPS for?
1: fedex.etrade.net.ph
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):1
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for fedex.etrade.net.ph
Enabled Apache socache_shmcb module
Enabled Apache ssl module
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. fedex.etrade.net.ph (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Timeout

 - The following errors were reported by the server:

   Domain: fedex.etrade.net.ph
   Type:   connection
   Detail: Timeout

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A 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): Apache/2.4.7

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

My hosting provider, if applicable, is: N/A (I don’t know yet)

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

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

trying to generate a certificate for one of our prod servers running apache and I encounter this error. How will I go about solving this issue? thanks

It looks like port 443 is not reaching your server.

thanks!! I can’t believe I missed that one. port 443 was closed because the default server we duplicated was using ufw and it opened only 80 and some other ports. Thanks again!

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