Cannot renew SSL

bash: nginx: command not found
[root@ip-172-31-32-163 ec2-user]# curl [ipconfig.me](http://ipconfig.me)
<HTML><HEAD><TITLE>Moved Permanently</TITLE></HEAD>
<BODY><H1>Moved Permanently</H1>
An error has occurred.
</BODY></HTML>[root@ip-172-31-32-163 ec2-user]# nslookup [crexspace.com](http://crexspace.com)
Server: 172.31.0.2
Address: 172.31.0.2#53
Non-authoritative answer:
Name: [crexspace.com](http://crexspace.com)
Address: 52.31.99.239
[root@ip-172-31-32-163 ec2-user]#

Got that whan I tried the comand


[root@ip-172-31-32-163 ec2-user]# certbot certonly
Saving debug log to /var/log/letsencrypt/letsencrypt.log
How would you like to authenticate with the ACME CA?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: Spin up a temporary webserver (standalone)
2: Place files in webroot directory (webroot)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate number [1-2] then [enter] (press 'c' to cancel): 1
Plugins selected: Authenticator standalone, Installer None
Please enter in your domain name(s) (comma and/or space separated) (Enter 'c'
to cancel): [www.crexspace.com](http://www.crexspace.com)
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for [www.crexspace.com](http://www.crexspace.com)
Waiting for verification...
Challenge failed for domain [www.crexspace.com](http://www.crexspace.com)
http-01 challenge for [www.crexspace.com](http://www.crexspace.com)
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: [www.crexspace.com](http://www.crexspace.com)
   Type: unauthorized
Detail: Invalid response from
[https://www.crexspace.com/.well-known/acme-challenge/c_qUxDzF83XM_VBXQ3JNyQeGG0YDVfrK0Ji06G5U1ZM](https://www.crexspace.com/.well-known/acme-challenge/c_qUxDzF83XM_VBXQ3JNyQeGG0YDVfrK0Ji06G5U1ZM)
   [52.31.99.239]: "<!DOCTYPE html><html lang=\"en\"
dir=\"ltr\"><head><meta charSet=\"utf-8\" class=\"next-head
next-head\"/><meta name=\"viewport\" content="
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.

I did this

Gives me below numbers

34.242.6.10

yes the developer said to log in as admin with sudo su

Hi Juergen

I did those with certbot certonly command. So they are active and my site will not be without SSL?

Then do it again.

Letsencrypt certificates are only 90 days valid. So if you have created the certificates manual, you have to re-do that every 60 - 85 days.

You're to fast.
I changed that to "IFconfig"
IPconfig forwards but doesn't really work.

TYPE IT IN MANUALLY - COPY/PASTE DOESN'T SEEM TO WORK WELL FOR YOU
curl ifconfig.me

What is that?

[ec2-user@ip-172-31-32-163 ~]$ curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[ec2-user@ip-172-31-32-163 ~]$ sudo su
[root@ip-172-31-32-163 ec2-user]# curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[root@ip-172-31-32-163 ec2-user]#

Good morning

I tried the command and it returns numbers: 34.242.6.10

[ec2-user@ip-172-31-32-163 ~]$ curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[ec2-user@ip-172-31-32-163 ~]$ sudo su
[root@ip-172-31-32-163 ec2-user]# curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[root@ip-172-31-32-163 ec2-user]#
[ec2-user@ip-172-31-32-163 ~]$ curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[ec2-user@ip-172-31-32-163 ~]$ sudo su
[root@ip-172-31-32-163 ec2-user]# curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[root@ip-172-31-32-163 ec2-user]#
[ec2-user@ip-172-31-32-163 ~]$ curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[ec2-user@ip-172-31-32-163 ~]$ sudo su
[root@ip-172-31-32-163 ec2-user]# curl [ifconfig.me](http://ifconfig.me)
34.242.6.10[root@ip-172-31-32-163 ec2-

Means you are probably on the WRONG system.

34.242.6.10 <> 52.31.99.239
[see: POST #16]

EDIT:
Both IPs are from Amazon [in Ireland]
So unless you work for Amazon [in Ireland], I can assume you got the IP from the system you are logged into (and not your own PC) and unless Amazon is forcing your curl request through a proxy the system you are now on is NOT the system that needs to be renewed.

Thanks ground control, was on wrong system…:wink: all good now.

3 Likes

All’s well that ends well Captain/Major :slight_smile:

1 Like

A post was merged into an existing topic: Renew SSL Certificate on Google DSN

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