![]() The following certificates could not be renewed: T08:56:16.161439+00:00 localhost certbot.renew: Failed to renew certificate with error: Some challenges have failed. T08:56:00.535921+00:00 localhost systemd: Starting - Service for snap application certbot.renew. T06:42:05.251236+00:00 localhost snapd: storehelpers.go:773: cannot refresh: snap has no updates available: "certbot", "core", "core20" ![]() All I know is that the renew worked OK after I removed the JkMount /atomik line from my sites-available config files, with that in, I was getting this from the snap job that runs daily: T04:12:04.926868+00:00 localhost snapd: storehelpers.go:773: cannot refresh: snap has no updates available: "certbot", "core", "core20" output of certbot -version or certbot-auto -version if you're using Certbot): certbot -version I can login to a root shell on my machine (yes or no, or I don't know): The operating system my web server runs on is (include version): crt.sh | ), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. Note: you must provide your domain name to get help. Please fill out the fields below so we can help you better. If I can access the script to add something that comments the JkMount line, that would be useful.Īlso if you have any tips on how to automatically renew on this context it will be much appreciated, maybe I'm missing something. I don't know the internals of the certbot and the auto-renew process, I just see on my logs that a cron runs daily trying to renew, and some snap stuff. ![]() Of course, after that, I need to uncomment everything manually again. Now my question: how can I automate the renewal without manually logging to the server and commenting the site config files? nf site file, just commented the JkMount line. **JkMount /* atomik <<< NEEDED TO COMMENT THIS**ĭid the same on the. The only way the cert renew worked, was by manually removing the configuration on the site*.conf files for the mod_jk that makes Apache talk to Tomcat, that is: ĮrrorLog /var/log/apache2/domains//error.logĬustomLog /var/log/apache2/domains//access.log combined We have Apache listening on ports 80/443 and forwarding to a Tomcat in the back via mod_jk ( Working with mod_jk) I have a test server and the auto-renew was failing (that's not the issue, see below).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |