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. crt.sh | 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:rocki.co.jp
I ran this command:sudo certbot certonly --manual -d rocki.co.jp
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Renewing an existing certificate for rocki.co.jp
It produced this output:- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Create a file containing just this data:
And make it available on your web server at this URL:
Press Enter to Continue
Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
Detail: 126.96.36.199: Invalid response from https://rocki.co.jp/.well-known/acme-challenge/IWAqmVE22BG_1AnaJrhu4LZfXbY6xUERqr6Ihp2rolE: 404
Hint: The Certificate Authority failed to verify the manually created challenge files. Ensure that you created these in the correct location.
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
However, since the beginning of this year, we have outsourced the management of our web pages to a third party and have set up an A-record.
Since the beginning of this year, we have outsourced the web page management to a third party and set the A record. After setting the A record, the SSL update of the WWW is done by the outsourced company and the SSL update of the hosting is done by us.
Before setting the A record, the file was created in /.well-known/acme-challenge in WWW, but after setting the A record, the file was created directly in rocki.co.jp and succeeded.
Also, this is the third update since the A record was set, but it did not succeed once, and when I perform the update after the expiration of the update deadline, the update is successful, although I do not know why.
Translated with DeepL Translate: The world's most accurate translator (free version)
My web server is (include version):Apache/2.4.56 (Unix)
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is:NTT COMMUNICATIONS
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):
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):certbot1.21.0