Return code: 429 Details: Error creating new order :: too many certificates (5)

Help
1

Hi 7 day has pass after and requesting 5 ssl certificate while setup my server and still no new ssl all domains are unavailable witch use letsencrypt ssl pls help

My domain is:
www.ogledalo.mk

My web server is (include version):
IPv4
157.90.228.37
IPv6
2a01:4f8:1c1c:4c10::/64
The operating system my web server runs on is (include version):
ubuntu 20.04

I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
ISP manager
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

2

No, only 5 days have passed. You got 5 certs on Mar5 so need to wait until Mar12 after 12:53UTC for one more try but best to wait until Mar13. Actually, best would be to use one that you already got on Mar5. See your history below.

Make sure you use the staging system when doing your next tests so this does not happen again

2 Likes
3

All domain under letsencrypt not working and only ogledalo.mk was with 5 cert how to restart all cenot wait 3 days need to bay new cert or

4

What domain names are not working?

2 Likes
5

Before issuing any more certificates, use the staging environment and make sure that whatever problem caused your first five certificates not to be usable (are they actually unusable? are they saved somewhere?) has been resolved.

Otherwise, you'll be a week later but not any closer to a solution.

2 Likes
6

laravel.mk, ogledalo.mk, zorandev.info

all domain are on the same server

7

Can you show an example URL that you think should be working? Because I don't see port 80 or port 443 open for any of these so http:// and https:// requests will fail.

Do you use an alternate port or have you closed these ports?

2 Likes
8 
server {
	server_name laravel.mk www.laravel.mk;
	charset UTF-8;
	index index.php index.html;
	disable_symlinks if_not_owner from=$root_path;
	include /etc/nginx/vhosts-includes/*.conf;
	include /etc/nginx/vhosts-resources/laravel.mk/*.conf;
	access_log /var/www/httpd-logs/laravel.mk.access.log;
	error_log /var/www/httpd-logs/laravel.mk.error.log notice;
	ssi on;
	set $root_path /var/www/www-root/data/www/laravel.mk;
	root $root_path;
	location / {
		location ~ [^/]\.ph(p\d*|tml)$ {
			try_files /does_not_exists @php;
		}
	}
	location @php {
		fastcgi_index index.php;
		fastcgi_param PHP_ADMIN_VALUE "sendmail_path = /usr/sbin/sendmail -t -i -f webmaster@laravel.mk";
		fastcgi_pass unix:/var/www/php-fpm/3.sock;
		fastcgi_split_path_info ^((?U).+\.ph(?:p\d*|tml))(/?.+)$;
		try_files $uri =404;
		include fastcgi_params;
	}
	listen 157.90.228.37:80;
}
server {
	server_name laravel.mk www.laravel.mk;
	ssl_certificate "/var/www/httpd-cert/www-root/laravel.mk_le1.crtca";
	ssl_certificate_key "/var/www/httpd-cert/www-root/laravel.mk_le1.key";
	ssl_ciphers EECDH:+AES256:-3DES:RSA+AES:!NULL:!RC4;
	ssl_prefer_server_ciphers on;
	ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3;
	ssl_dhparam /etc/ssl/certs/dhparam4096.pem;
	charset UTF-8;
	index index.php index.html;
	disable_symlinks if_not_owner from=$root_path;
	include /etc/nginx/vhosts-includes/*.conf;
	include /etc/nginx/vhosts-resources/laravel.mk/*.conf;
	access_log /var/www/httpd-logs/laravel.mk.access.log;
	error_log /var/www/httpd-logs/laravel.mk.error.log notice;
	ssi on;
	set $root_path /var/www/www-root/data/www/laravel.mk;
	root $root_path;
	location / {
		location ~ [^/]\.ph(p\d*|tml)$ {
			try_files /does_not_exists @php;
		}
	}
	location @php {
		fastcgi_index index.php;
		fastcgi_param PHP_ADMIN_VALUE "sendmail_path = /usr/sbin/sendmail -t -i -f webmaster@laravel.mk";
		fastcgi_pass unix:/var/www/php-fpm/3.sock;
		fastcgi_split_path_info ^((?U).+\.ph(?:p\d*|tml))(/?.+)$;
		try_files $uri =404;
		include fastcgi_params;
	}
	listen 157.90.228.37:443 ssl http2;
}

my config nginx is lisining on 80 and 443 after ssl problem stop responding

9

Usually is best to use *:80 and *:443 instead of using the IP address.

But, as I said, Neither of these ports is open. I am not familiar with ISPconfig but do you need to open these ports there? See:

I also see this (note no port 80 or 443). nginx may be listening but then it is getting blocked before that. What happens with this command:

sudo nginx -t

Port status:

PORT     STATE SERVICE
21/tcp   open  ftp
22/tcp   open  ssh
25/tcp   open  smtp
53/tcp   open  domain
110/tcp  open  pop3
143/tcp  open  imap
465/tcp  open  smtps
587/tcp  open  submission
993/tcp  open  imaps
995/tcp  open  pop3s
2 Likes
10 
root@mkdhost:~# ufw status verbose
Status: active
Logging: on (low)
Default: deny (incoming), allow (outgoing), disabled (routed)
New profiles: skip

To                         Action      From
--                         ------      ----
80/tcp                     ALLOW IN    Anywhere                  
443/tcp                    ALLOW IN    Anywhere                  
80,443/tcp (Nginx Full)    ALLOW IN    Anywhere                  
80/tcp (v6)                ALLOW IN    Anywhere (v6)             
443/tcp (v6)               ALLOW IN    Anywhere (v6)             
80,443/tcp (Nginx Full (v6)) ALLOW IN    Anywhere (v6)
11

when tray to open domain get Secure Connection Failed

12

Can you show result of that command? Port 80 is still not open to the public internet.

2 Likes
13

This two-step process seems unnecessary:

Why can't you use?:
root /var/www/www-root/data/www/laravel.mk;

1 Like
14

root@mkdhost:~# sudo nginx -t
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful

15

@KalimeroMK All you show looks ok but still cannot connect to your sites with either http or https. Ports 80 and port 443 are blocked somewhere. I also see port 25 block right now if that is a clue.

Can you show the output of these commands

sudo netstat -pant | grep -i listen
sudo systemctl status nginx
2 Likes
16

force restart of the server fix it :smile:

1 Like
17

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