Jump to content
Froxlor Forum
  • 0
kingsley ezenwa

SSL not working on FROXLOR api enabled version

Question

Before now, SSL has been working perfectly okay using FROXLOR but since upgrading to FROXLOR v0.10.0  , i noticed that though old domains already with SSL continues working, new domains registered for LetsEncrypt SSL under the new FROXLOR version isn't working with regards to SSL.

Below is output of    php /var/www/FROXLOR/scripts/froxlor_master_cronjob.php --letsencrypt --debug

 

PHP Warning:  Module 'apcu' already loaded in Unknown on line 0
[information] Updating Let's Encrypt certificates
[information] Updating example.com
[information] Adding SAN entry: example.com
[information] Adding SAN entry: www.example.com
[information] letsencrypt Using 'https://acme-v01.api.letsencrypt.org' to generate certificate
[information] letsencrypt Using existing account key
[information] letsencrypt Starting certificate generation process for domains
[information] letsencrypt Requesting challenge for example.com
[information] letsencrypt Sending signed request to /acme/new-authz
[error] Could not get Let's Encrypt certificate for example.com: No challenges received for example.com. Whole response: {"type":"urn:acme:error:rateLimited","detail":"Error creating new authz :: too many failed authorizations recently: see https:\/\/letsencrypt.org\/docs\/rate-limits\/","status":429} 

 

 

Kindly do point me in the right direction if am making any mistake.

Have compared the domain setting with those working with ssl and they are all same.

Thanks

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0
16 minutes ago, kingsley ezenwa said:

{"type":"urn:acme:error:rateLimited","detail":"Error creating new authz :: too many failed authorizations recently: see https:\/\/letsencrypt.org\/docs\/rate-limits\/","status":429} 

Says all, has nothing to do with froxlor. Also there were no changes in the certificate creation between 0.9.x and 0.10.0 - also keep in mind that 0.10.0 is not even Beta and should not be used in production

Share this post


Link to post
Share on other sites
  • 0
3 minutes ago, d00p said:

Says all, has nothing to do with froxlor. Also there were no changes in the certificate creation between 0.9.x and 0.10.0 - also keep in mind that 0.10.0 is not even Beta and should not be used in production

okay

 

so what you think might be the issue  ?
 

this is a domain that has been running without SSL for long and only decided to add SSL to it today .

Share this post


Link to post
Share on other sites
  • 0

Let's encrypt tells you in the error message: too  many failed authorizations recently: 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×