Connection Refused with Certbot

My domain is: pynamibia.org

I ran this command: certbot --apache certonly

It produced this output: (I do realize that my main problem is that the site doesn’t listen on 443, but I’m not sure what to do about it.)

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

Plugins selected: Authenticator apache, Installer apache

Which names would you like to activate HTTPS for?

1: pynamibia.org

Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter ‘c’ to cancel):
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for pynamibia.org
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. pynamibia.org (tls-sni-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Connection refused

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: pynamibia.org
    Type: connection
    Detail: Connection refused

    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): httpd (apache)

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

My hosting provider, if applicable, is: Linode

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

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

Your domain offers IPv4 and IPv6 address records, but your server does not accept IPv6 connections to port 443.

Since IPv6 has higher precedence, the timeout occurs.
To fix that, either drop the IPv6 records or have a look into firewall rules which deny access via IPv6.

2 Likes

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