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:rubberboard.gov.in and rubberboard.org.in
I ran this command:rubberboard.gov.in working fine.
It produced this output:need to know since both names are same did it work or cause any issue
My web server is (include version):tomcat 8.5.56
The operating system my web server runs on is (include version):rhel 7.6
My hosting provider, if applicable, is:
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):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):using getssl for free site
Your certificate must include the name used in the URL
https://rubberboard.gov.in works
https://rubberboard.org.in fails as it is using the ...gov.in cert
You probably need to configure Tomcat for the rubberboard.org.in names and then get and use a cert with those names. Just do the same as you did for gov.in.
Does that site allow you to request multiple domain names in a single certificate? Let's Encrypt allows this but individual tools to request certificates might not provide this functionality.
A single Let's Encrypt certificate can cover up to 100 names. Each name under which people access your web site should be listed in your certificate. It is also possible to obtain multiple separate certificates for the separate names, and most web server software can be configured to select the appropriate one when each connection arrives.
The most recommended way to get and manage Let's Encrypt certificates is to install a client application on your web server, which should be possible if you're the server administrator.
With Tomcat, many people have had good results using a reverse proxy in front of Tomcat, such as Caddy. Caddy can obtain Let's Encrypt certificates automatically for every domain name that your site uses, can receive the inbound connections over HTTPS, and can easily be configured to forward them to a different TCP port on localhost, where Tomcat is listening. In this scenario you would not have to install any certificates in Tomcat at all.