I cant install SSL and i Get Error

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: https://job.ngo

I ran this command: Wildcard SSL

It produced this output: job.ngo

SSL Manager

Using SSL is crucial for the security of your website. The SSL certificate encrypts all traffic that goes through your website and ensures that sensitive information like login credentials and credit card details remains protected. Use the SSL Manager to easily install different SSL certificates, import existing ones, and manage all active certificates for your site in one place.

Read More

Install New SSL

Failed to install Let’s Encrypt for job.ngo .

ERROR: acmebot->create_new_order: Net::ACME2::x::ACME: “https://acme-v02.api.letsencrypt.org/acme/new-order” indicated an ACME error: 429 Too Many Requests (429 urn:ietf:params:acme:error:rateLimited (The request exceeds a rate limit) (Error creating new order :: too many certificates already issued for exact set of domains: .job.ngo,job.ngo: see https://letsencrypt.org/docs/rate-limits/)). ==> Net::ACME2::x::Generic::new(‘Net::ACME2::x::ACME’, ‘“https://acme-v02.api.letsencrypt.org/acme/new-order” indicated an ACME error: 429 Too Many Requests (429 urn:ietf:params:acme:error:rateLimited (The request exceeds a rate limit) (Error creating new order :: too many certificates already issued for exact set of domains: .job.ngo,job.ngo: see https://letsencrypt.org/docs/rate-limits/)).’, HASH(0x455e3f0)) (called in /usr/local/lib64/perl5/Net/ACME2/X/ACME.pm at line 31) ==> Net::ACME2::x::ACME::new(‘Net::ACME2::x::ACME’, HASH(0x455e3f0)) (called in /usr/local/lib64/perl5/X/Tiny.pm at line 169) ==> X::Tiny::create(‘Net::ACME2::X’, ‘ACME’, HASH(0x455e3f0)) (called in /usr/local/lib64/perl5/Net/ACME2/HTTP.pm at line 159) ==> Net::ACME2::HTTP::_request(Net::ACME2::HTTP=HASH(0x42a70e0), ‘POST’, ‘https://acme-v02.api.letsencrypt.org/acme/new-order’, HASH(0x4525e10), HASH(0x45410c0)) (called in /usr/local/lib64/perl5/Net/ACME2/HTTP.pm at line 181) ==> Net::ACME2::HTTP::_request_and_set_last_nonce(Net::ACME2::HTTP=HASH(0x42a70e0), ‘POST’, ‘https://acme-v02.api.letsencrypt.org/acme/new-order’, HASH(0x4525e10), HASH(0x45410c0)) (called in /usr/local/lib64/perl5/Net/ACME2/HTTP.pm at line 108) ==> Net::ACME2::HTTP::_post(Net::ACME2::HTTP=HASH(0x42a70e0), ‘create_key_id_jws’, ‘https://acme-v02.api.letsencrypt.org/acme/new-order’, HASH(0x4407ec0)) (called in /usr/local/lib64/perl5/Net/ACME2/HTTP.pm at line 88) ==> Net::ACME2::HTTP::post_key_id(Net::ACME2::HTTP=HASH(0x42a70e0), ‘https://acme-v02.api.letsencrypt.org/acme/new-order’, HASH(0x4407ec0)) (called in /usr/local/lib64/perl5/Net/ACME2.pm at line 555) ==> Net::ACME2::_post_url(Net::ACME2::LetsEncrypt=HASH(0x42a7b70), ‘https://acme-v02.api.letsencrypt.org/acme/new-order’, HASH(0x4407ec0), undef) (called in /usr/local/lib64/perl5/Net/ACME2.pm at line 537) ==> Net::ACME2::_post(Net::ACME2::LetsEncrypt=HASH(0x42a7b70), ‘newOrder’, HASH(0x4407ec0)) (called in /usr/local/lib64/perl5/Net/ACME2.pm at line 315) ==> Net::ACME2::create_order(Net::ACME2::LetsEncrypt=HASH(0x42a7b70), ‘identifiers’, ARRAY(0x4593a48)) (called in /usr/local/lib64/perl5/Acmebot.pm at line 94) ==> (eval)(Net::ACME2::LetsEncrypt=HASH(0x42a7b70), ‘identifiers’, ARRAY(0x4593a48)) (called in /usr/local/lib64/perl5/Acmebot.pm at line 93) ==> Acmebot::create_order(Net::ACME2::LetsEncrypt=HASH(0x42a7b70), ‘/etc/letsencrypt/authzs/1589032294.authzs’, ‘job.ngo’, '.job.ngo’) (called in /usr/local/lib64/perl5/Acmebot.pm at line 182) ==> Acmebot::order_certs(Net::ACME2::LetsEncrypt=HASH(0x42a7b70), ‘/etc/letsencrypt/authzs/1589032294.authzs’, ‘DNS’, HASH(0x4460af8), ‘job.ngo’, '.job.ngo’) (called in /usr/local/lib64/perl5/Acmebot.pm at line 237) ==> Acmebot::issue_cert(HASH(0x45880f0), HASH(0x456a7c0)) (called in lib/Avalon/Ssl.pm at line 473) ==> (eval)(HASH(0x45880f0), HASH(0x456a7c0)) (called in lib/Avalon/Ssl.pm at line 473) ==> Avalon::Ssl::issue_le(DBI::db=HASH(0x457ddb0), HASH(0x39a4500), HASH(0x4516ec0)) (called in lib/Avalon/Ssl.pm at line 536) ==> Avalon::Ssl::create_le(HASH(0x39b5cb8), HASH(0x4516ec0)) (called in /home/avalon/avalon/workers/…/lib/Avalon/Utils/jobs.pm at line 186) ==> (eval)(HASH(0x39b5cb8), HASH(0x4516ec0)) (called in /home/avalon/avalon/workers/…/lib/Avalon/Utils/jobs.pm at line 185) ==> Avalon::Utils::jobs::task_execute(HASH(0x39b5cb8)) (called in /home/avalon/avalon/workers/worker.pl at line 86) ==> main::do_task(HASH(0x39b5cb8)) (called in /home/avalon/avalon/workers/worker.pl at line 108) ==> main::api_task_router(Gearman::Job=HASH(0x3f6b230)) (called in /usr/local/lib64/perl5/Gearman/Worker.pm at line 344) ==> (eval)(Gearman::Job=HASH(0x3f6b230)) (called in /usr/local/lib64/perl5/Gearman/Worker.pm at line 344) ==> Gearman::Worker::work(Gearman::Worker=HASH(0x396dba0)) (called in /home/avalon/avalon/workers/worker.pl at line 190) ==> main::main(‘main’) (called in /home/avalon/avalon/workers/worker.pl at line 41)

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: Siteground

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

1 Like

Hi @Ahmadi1,

If you’re using managed hosting on Siteground and you use a control panel to configure it, you’ll need to ask Siteground’s support for help with this because it is probably due to some kind of misconfiguration or error in Siteground’s own systems.

The exception is if you were previously hosting this site elsewhere and mistakenly issued a high volume of identical certificates on your other hosting. In that case you would probably want to way for one week for the Let’s Encrypt issuance rate limits to be reset.

If it has only been hosted in its present form on Siteground recently, I would suggest asking Siteground’s support to help figure out this problem; it seems like you’ve probably used their system correctly but their system isn’t functioning properly.

If you administer the site yourself with some kind of dedicated or advanced plan, you’ll need to give us some more details of your hosting environment and how you host and run the site.


1 Like

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