Skip to content

SSL certificate renewal has failed #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
josecelano opened this issue Mar 2, 2025 · 1 comment
Closed

SSL certificate renewal has failed #34

josecelano opened this issue Mar 2, 2025 · 1 comment
Assignees

Comments

@josecelano
Copy link
Member

Automatic renewal of HTTPs certificates has failed. I have tried to run the script manually and It has also failed:

./share/bin/ssl_renew.sh 
Container tracker  Running
Container prometheus  Running
Container grafana  Running
Container index  Running
Container index-gui  Running
Container proxy  Running
Container certbot  Starting
Container certbot  Started
Saving debug log to /var/log/letsencrypt/letsencrypt.log

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/grafana.torrust-demo.com.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for grafana.torrust-demo.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: grafana.torrust-demo.com
  Type:   connection
  Detail: 144.126.245.19: Fetching http://grafana.torrust-demo.com/.well-known/acme-challenge/mnno83WbqDDheoxR0fHzCnBpQBYgWfJq-Wb8SQXI-3c: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Failed to renew certificate grafana.torrust-demo.com with error: Some challenges have failed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/index.torrust-demo.com-0001.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for index.torrust-demo.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: index.torrust-demo.com
  Type:   connection
  Detail: 144.126.245.19: Fetching http://index.torrust-demo.com/.well-known/acme-challenge/ih6qJRxe5MuEkXppUU9iB8KA40EY2L5MiG8sAI93yE8: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Failed to renew certificate index.torrust-demo.com-0001 with error: Some challenges have failed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/index.torrust-demo.com.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for index.torrust-demo.com and tracker.torrust-demo.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: index.torrust-demo.com
  Type:   connection
  Detail: 144.126.245.19: Fetching http://index.torrust-demo.com/.well-known/acme-challenge/05defVWyWvbyqHzT3OAh2xGioV85xGdgP_WnzYtXkRU: Timeout during connect (likely firewall problem)

  Domain: tracker.torrust-demo.com
  Type:   connection
  Detail: 144.126.245.19: Fetching http://tracker.torrust-demo.com/.well-known/acme-challenge/ZdLIczvnMzCrGB2s32KjsDPMsLF-t0ILPnzwl5vhetU: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Failed to renew certificate index.torrust-demo.com with error: Some challenges have failed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/tracker.torrust-demo.com.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for tracker.torrust-demo.com

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: tracker.torrust-demo.com
  Type:   connection
  Detail: 144.126.245.19: Fetching http://tracker.torrust-demo.com/.well-known/acme-challenge/oAJ3jT1gLBdwo8LFUjVq2VdXbtUaU0cOR1HFDiyyStA: Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to download the temporary challenge files created by Certbot. Ensure that the listed domains serve their content from the provided --webroot-path/-w and that files created there can be downloaded from the internet.

Failed to renew certificate tracker.torrust-demo.com with error: Some challenges have failed.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All renewals failed. The following certificates could not be renewed:
  /etc/letsencrypt/live/grafana.torrust-demo.com/fullchain.pem (failure)
  /etc/letsencrypt/live/index.torrust-demo.com-0001/fullchain.pem (failure)
  /etc/letsencrypt/live/index.torrust-demo.com/fullchain.pem (failure)
  /etc/letsencrypt/live/tracker.torrust-demo.com/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
4 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

I think it's because I closed the port 80.

@josecelano
Copy link
Member Author

I opened the port 80 and run it manually again. The port has to be open unless we implement a different challenge type. See #35

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant