Follow-up to this thread:
I found the problem, which was my own mistake. I failed to enter the correct
domain name when creating the keystone. After going back through the entire
process again, with the correct domain name, the server is up and running
again. Thanks, nevertheless, for the
Ralph,
On 3/21/23 06:38, Ralph Grove wrote:
> [snip]
>
Alias name: tomcat
Creation date: Mar 21, 2023
Entry type: trustedCertEntry
You created a keystore with no keys.
Where is the key you used to generate the CSR? That key needs to be in
your keystore under the alias 'tomcat' alongside
> On Mar 21, 2023, at 4:25 AM, Mark Thomas wrote:
>
> On 21/03/2023 01:09, Ralph Grove wrote:
>> I'm having a problem installing a new SSL certificate on a GoDaddy-hosted
>> server running Tomcat. Any suggestions for resolving it would be appreciated.
>> I set up the server last year and
On 21/03/2023 01:09, Ralph Grove wrote:
I'm having a problem installing a new SSL certificate on a GoDaddy-hosted
server running Tomcat. Any suggestions for resolving it would be appreciated.
I set up the server last year and installed the SSL certificate with no problem. This
year, after the
Pressed send too quickly -- I see different aliases there. Ignore my
previous comments
Using PEM files is much simpler to manage, I would go that route instead...
will make it easier. However, I can't offer any real advice on the specific
issue at this time...
Others will certainly be more
I believe the default certificate alias used by Tomcat is "tomcat". I think
you are creating your keystore with the alias "root".
(see https://tomcat.apache.org/tomcat-9.0-doc/ssl-howto.html for docs on
Tomcat SSL configuration -- adjust for the version you are running)
On Mon, Mar 20, 2023 at
I'm having a problem installing a new SSL certificate on a GoDaddy-hosted
server running Tomcat. Any suggestions for resolving it would be appreciated.
I set up the server last year and installed the SSL certificate with no
problem. This year, after the original certificate expired, I
