My domain is: helokev.asuscomm.com
I ran this command: I recreated the same domain name on my router to resolve the problem, but it didn't change anything. I tried to create another domain name but nothing changed either
It produced this output: I have a status showing "allow" but the update and expiration dates do not appear
My web server is (include version): asuscomm.com on my Asus AC68U router
The operating system my web server runs on is (include version): asuscomm.com on my Asus AC68U router
My hosting provider, if applicable, is: asuscomm.com
I can login to a root shell on my machine (yes or no, or I don't know): yes « putty »
I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot): i don’t know
Here is the history of the system:
Dec 6 16:59:12 kernel: [Sun Dec 6 16:59:12 MET 2020] Registering account
Dec 6 16:59:17 kernel: [Sun Dec 6 16:59:17 MET 2020] Already registered
Dec 6 16:59:17 kernel: [Sun Dec 6 16:59:17 MET 2020] ACCOUNT_THUMBPRINT='REMPvW_WodaH0Ppxj3OF4irdWVV0SaCRXlo-10XUJRw'
Dec 6 16:59:17 kernel: [Sun Dec 6 16:59:17 MET 2020] Single domain='helokev.asuscomm.com'
Dec 6 16:59:18 kernel: [Sun Dec 6 16:59:18 MET 2020] Getting domain auth token for each domain
Dec 6 16:59:21 kernel: [Sun Dec 6 16:59:21 MET 2020] Create new order error. Le_OrderFinalize not found. {
Dec 6 16:59:21 kernel: "type": "urn:ietf:params:acme:error:rateLimited",
Dec 6 16:59:21 kernel: "detail": "Error creating new order :: too many certificates already issued for exact set of domains: helokev.asuscomm.com: see https://letsencrypt.org/docs/rate-limits/",
Dec 6 16:59:21 kernel: "status": 429
Dec 6 16:59:21 kernel: }
Dec 6 16:59:21 kernel: [Sun Dec 6 16:59:21 MET 2020] Please add '--debug' or '--log' to check more details.
Dec 6 16:59:21 kernel: [Sun Dec 6 16:59:21 MET 2020] See: https://github.com/Neilpang/acme.sh/wiki/How-to-debug-acme.sh
Dec 6 16:59:29 rc_service: watchdog 322:notify_rc start_cfgsync
Dec 6 16:59:59 rc_service: watchdog 322:notify_rc start_cfgsync
Dec 6 17:00:29 rc_service: watchdog 322:notify_rc start_cfgsync
Dec 6 17:00:59 rc_service: watchdog 322:notify_rc start_cfgsync
Dec 6 17:01:29 rc_service: watchdog 322:notify_rc start_cfgsync
Dec 6 17:01:59 rc_service: watchdog 322:notify_rc start_cfgsync