Certbot failed, can not get IP Address

Perfect. I can see the A record now for weroc.co.

Now try generating your certificate again.

It’s working. No need to wait.

Excellent! Many people struggle with doing that.

Failed a bit different
Domain weroc.co
Type unauthorized
Detail: Invalid responce for http:/weroc.com.well known/acme . . . . .
To fix errors make sure domain name was correctly entered and the DNS A/AAA record(s) contains the right IP

Can you please post the entire result. I need to run for a few minutes.

The get certsonly ran to completion, once I ran it with the right IP, but https would not work. Now I have it repaired (back to port 80) and need to rerun the whole install on the production system.

How would you rerun it . ? This is nginx running hls.

sudo certbot install --nginx

Remember to restart nginx afterwards to use your new certificate.

I ran: ```
sudo certbot --nginx certonly

certonly doesn’t install the certificate.

How would you suggest doing this, I’ve never successfully done this before.

1 Like

You should be able to just run sudo certbot --nginx without the certonly. That way certbot can (try to) install the certificate for you and generate a HTTPS virtualhost on port 443.

1 Like

That was a total mess, took the system down:
Which names would you like to activate HTTPS for?


1: weroc.com
2: www.weroc.com


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:
http-01 challenge for weroc.com
http-01 challenge for www.weroc.com
nginx: [error] invalid PID number “” in “/run/nginx.pid”
Waiting for verification…
Challenge failed for domain weroc.com
Challenge failed for domain www.weroc.com
http-01 challenge for weroc.com
http-01 challenge for www.weroc.com
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: weroc.com
    Type: connection
    Detail: Fetching
    http://weroc.com/.well-known/acme-challenge/gW3dg2t7ANob0A1p7aW7Rs4aWdZEfrwslhU1vRSSLuA:
    Error getting validation data

    Domain: www.weroc.com
    Type: connection
    Detail: Fetching
    http://www.weroc.com/.well-known/acme-challenge/EWIbIkHKRZEcNh-d09qb17J2EM2DcsJNLF5tp0w3qZ4:
    Error getting validation data

    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.

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

1 Like

That error is presented when nginx was down when certbot ran. Any idea why nginx is down? That's not something that certbot would have caused.

1 Like

Dah, I turned it off so that it would not interfere. I’m starting to go nuts with this.
I’ll retry with Nginx SERVER on and OSB off.

1 Like

With nginx running

Which names would you like to activate HTTPS for?


1: weroc.com
2: www.weroc.com


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:
http-01 challenge for weroc.com
http-01 challenge for www.weroc.com
Waiting for verification…
Challenge failed for domain weroc.com
Challenge failed for domain www.weroc.com
http-01 challenge for weroc.com
http-01 challenge for www.weroc.com
Cleaning up challenges
Some challenges have failed.

IMPORTANT NOTES:

I’m getting that port 80 is closed for both weroc.com and www.weroc.com.

Is nginx actually running?

Ok it’s not com but co, so I’ve corrected /etc/nginx/sites-available/default

It’s been really confusing, cause I’ve never worked anything but .com’s and totally missed this. You’re really helping me think through this.

It’s working and I just fixed the stream addresses which were pointing to http! It’s up and running 100%. Thanks much to all that helped. It time to drop it down and clone the disk!

Again thanks

2 Likes

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