Seleccionar página

[root@ip-172-30-2-236 letsencryt]

# systemctl stop firewalld

[root@ip-172-30-2-236 letsencryt]

# systemctl status firewalld
● firewalld.service – firewalld – dynamic firewall daemon
Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
Active: inactive (dead) since jue 2019-01-17 11:59:00 UTC; 6s ago
Docs: man:firewalld(1)
Process: 2443 ExecStart=/usr/sbin/firewalld –nofork –nopid $FIREWALLD_ARGS (code=exited, status=0/SUCCESS)
Main PID: 2443 (code=exited, status=0/SUCCESS)

ene 17 10:40:46 ip-172-30-2-236.eu-west-1.compute.internal systemd[1]: Starting firewalld – dynamic firewall daemon…
ene 17 10:40:47 ip-172-30-2-236.eu-west-1.compute.internal systemd[1]: Started firewalld – dynamic firewall daemon.
ene 17 11:58:59 ip-172-30-2-236.eu-west-1.compute.internal systemd[1]: Stopping firewalld – dynamic firewall daemon…
ene 17 11:59:00 ip-172-30-2-236.eu-west-1.compute.internal systemd[1]: Stopped firewalld – dynamic firewall daemon.

[root@ip-172-30-2-236 letsencryt]

# sudo certbot certonly –standalone –preferred-challenges http –agree-tos –email info@robinrover.com -d api.robinrover.com -d auth.robinrover.com -d unifiedpush.robinrover.com –staging -n
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Starting new HTTPS connection (1): acme-staging-v02.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for api.robinrover.com
http-01 challenge for auth.robinrover.com
http-01 challenge for unifiedpush.robinrover.com
Waiting for verification…
Cleaning up challenges
Resetting dropped connection: acme-staging-v02.api.letsencrypt.org

IMPORTANT NOTES:

  • Congratulations! Your certificate and chain have been saved at:
    /etc/letsencrypt/live/api.robinrover.com/fullchain.pem
    Your key file has been saved at:
    /etc/letsencrypt/live/api.robinrover.com/privkey.pem
    Your cert will expire on 2019-04-17. To obtain a new or tweaked
    version of this certificate in the future, simply run certbot
    again. To non-interactively renew all of your certificates, run
    “certbot renew”

[root@ip-172-30-2-236 letsencryt]

# sudo certbot certonly –standalone –preferred-challenges http –agree-tos –email info@robinrover.com -d api.robinrover.com -d auth.robinrover.com -d unifiedpush.robinrover.com –staging -n^C

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/api.robinrover.com/cert.pem
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Enter email address (used for urgent renewal and security notices) (Enter ‘c’ to
cancel):
Invalid email address: .
Enter email address (used for urgent renewal and security notices)

If you really want to skip this, you can run the client with
–register-unsafely-without-email but make sure you then backup your account key
from /etc/letsencrypt/accounts

(Enter ‘c’ to cancel): info@robinrover.com
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org


Please read the Terms of Service at
https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf. You must
agree in order to register with the ACME server at
https://acme-v02.api.letsencrypt.org/directory


(A)gree/(C)ancel: A


Would you be willing to share your email address with the Electronic Frontier
Foundation, a founding partner of the Let’s Encrypt project and the non-profit
organization that develops Certbot? We’d like to send you email about our work
encrypting the web, EFF news, campaigns, and ways to support digital freedom.


(Y)es/(N)o: Y
Starting new HTTPS connection (1): supporters.eff.org
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
An unexpected error occurred:
The request message was malformed :: No such certificate
Please see the logfiles in /var/log/letsencrypt for more details.

IMPORTANT NOTES:

  • 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.
  • We were unable to subscribe you the EFF mailing list because your
    e-mail address appears to be invalid. You can try again later by
    visiting https://act.eff.org.

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/auth.robinrover.com/cert.pem
usage:
certbot [SUBCOMMAND] [options] [-d DOMAIN] [-d DOMAIN] …

Certbot can obtain and install HTTPS/TLS/SSL certificates. By default,
it will attempt to use a webserver both for obtaining and installing the
certificate.
certbot: error: argument –cert-path: No such file or directory

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/
api.robinrover.com/ README

[root@ip-172-30-2-236 letsencryt]

# certbot revoke –cert-path /etc/letsencrypt/live/api.robinrover.com/cert.pem
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
An unexpected error occurred:
The request message was malformed :: No such certificate
Please see the logfiles in /var/log/letsencrypt for more details.

[root@ip-172-30-2-236 letsencryt]

# certbot delete –cert-name api.robinrover.com
Saving debug log to /var/log/letsencrypt/letsencrypt.log


Deleted all files relating to certificate api.robinrover.com.


[root@ip-172-30-2-236 letsencryt]

#

 

Comparte este post si te ha resultado útil, así quizás puedas ayudar a alguien que lo necesite.

¡Gracias por tu difusión!

Este sitio web utiliza cookies para que usted tenga la mejor experiencia de usuario. Si continúa navegando está dando su consentimiento para la aceptación de las mencionadas cookies y la aceptación de nuestra política de cookies, pinche el enlace para mayor información.plugin cookies

ACEPTAR
Aviso de cookies

Pin It on Pinterest