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.
Use a web server as a reverse proxy to your application (e.g. nginx or Caddy). Then you can obtain your certificate and terminate TLS at the reverse proxy.
Use Certbot's --standalone feature. You will have to temporarily stop your application when requesting and renewing certificates, because --standalone needs port 80 for itself. You may be able to automate the stopping and restarting of your application by specifying commands to Certbot's --pre-hook and --post-hook options.
Hi Thanks for the reply.
To use the standalone cmd, I need to install certbot in the same instance in which my application is running right?
Because currently I’m using -manual as certbot is running on machine other than my target webserver
Hi Thanks for the reply.
To use the standalone cmd, I need to install certbot in the same instance in which my application is running right?
Because currently Iâm using -manual as certbot is running on machine other than my target webserver
Yes, that's correct. Certbot is most able to automate the certificate request and deployment process when it's running on the same machine where the web server is located.
Hi thank you.This solution worked for generating the certificate successfully. But when I use the certificate it’s showing certificate is invalid in the browser.
Any idea why this could happen?
When you renew your certificate, the files will be updated but you need to ensure your tomcat configuration is pointing to the latest files. Normally this is via a symbolic link.
You also need to restart tomcat when your cert files change.
It would be great to know your real domain name so that we could check on the problem for ourselves.
I forgot if you said whether you're using Tomcat with a JKS or with PEM files, but one thing to consider is that, when you do a renewal with Certbot, Certbot will only save updated PEM files. If you happen to have created a JKS file based on those PEM files, you'll have to update your JKS file, too.
Certify The Web also has a Deploy to Tomcat option (Task), just so you know. It requires a version of tomcat that works with PKCS12 certificate containers (e.g. PFX). It can also restart tomcat.