Skip to content
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

Suddenly SSL certificate not generate #4673

Open
wpdevninja opened this issue Dec 26, 2024 · 6 comments
Open

Suddenly SSL certificate not generate #4673

wpdevninja opened this issue Dec 26, 2024 · 6 comments
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.

Comments

@wpdevninja
Copy link

Error Message and Logs

Adding new application not generating SSL certificate. This the log from proxy

2024-12-25T13:40:35.756848275Z 2024-12-25T13:40:35Z ERR Unable to obtain ACME certificate for domains error="unable to generate a certificate for the domains [xyz.domain.com]: acme: error: 429 :: POST :: https://acme-v02.api.letsencrypt.org/acme/new-order :: urn:ietf:params:acme:error:rateLimited :: too many failed authorizations (5) for "xyz.domain.com" in the last 1h0m0s, retry after 2024-12-25 13:44:25 UTC: see https://letsencrypt.org/docs/rate-limits/#authorization-failures-per-hostname-per-account" ACME CA=https://acme-v02.api.letsencrypt.org/directory acmeCA=https://acme-v02.api.letsencrypt.org/directory domains=["xyz.domain.com"] providerName=letsencrypt.acme routerName=https-0-v4888sc040sks8oskgoowsg4-wordpress@docker rule="Host(xyz.domain.com) && PathPrefix(/)"

Steps to Reproduce

  1. Add new application
  2. Edit the domain to my desired domain
  3. Deploy
  4. Go to the link & it says "Invalid SSL certificate"

Example Repository URL

No response

Coolify Version

v4.0.0-beta.379

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 22.04

Additional Information

No response

@wpdevninja wpdevninja added 🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization. labels Dec 26, 2024
@farhan2401
Copy link

This also happen to me. I change cloudflare from full(strict) to full for now and it works. Not sure why this happen

@wpdevninja
Copy link
Author

This also happen to me. I change cloudflare from full(strict) to full for now and it works. Not sure why this happen

I also change strict to full. Nothing works.

@wpdevninja
Copy link
Author

This also happen to me. I change cloudflare from full(strict) to full for now and it works. Not sure why this happen

@farhan2401 Do you experience the same error?

@farhan2401
Copy link

farhan2401 commented Dec 27, 2024

Image
This is what i can see on my proxy. Then i change from strict to full and click save and i can access my site again
Image

@farhan2401
Copy link

After you change to full. Wait like 30 sec and try open your site in incognito

@wpdevninja
Copy link
Author

This is a different error than mine. Mine was "too many failed authorizations " 430.
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Reported issues that need to be reproduced by the team. 🔍 Triage Issues that need assessment and prioritization.
Projects
None yet
Development

No branches or pull requests

2 participants