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 help.
Ralph > On Mar 21, 2023, at 6:38 AM, Ralph Grove <rfgr...@icloud.com> wrote: > >>> I set up the server last year and installed the SSL certificate with no >>> problem. This year, after the original certificate expired, I downloaded >>> the new certificate provided by GoDaddy, removed the old certificate files >>> from the keystore, and installed the new ones. Now Tomcat is throwing a >>> "java.io.IOException: jsse.alias_no_key_entry" exception when it tries to >>> open the HTTPS connector. I also tried rebuilding the keystore from scratch >>> and requesting a new certificate, but am getting the same exception with >>> that certificate. >>> These are the commands I used to obtain and install the certificate: >>> sudo keytool -genkey -alias tomcat -keyalg RSA -keystore keystore.jks >>> sudo keytool -certreq -keyalg RSA -alias tomcat -file certreq.csr -keystore >>> keystore.jks >>> (--request and obtain certificate files from GoDaddy--) >> >> Did you run the commands below on the same keystore file you created in the >> first command above? > > Yes - it was the same file. I went through the commands twice, just to be > sure. >> >>> sudo keytool -import -alias root -keystore keystore.jks -trustcacerts -file >>> gdcerts/gdroot-g2.crt >>> sudo keytool -import -alias inter -keystore keystore.jks -trustcacerts >>> -file gdcerts/gd_bundle-g2-g1.crt >>> sudo keytool -import -alias tomcat -keystore keystore.jks -file >>> gdcerts/xxxxxxxxxxxx.crt >> >> What is the output of: >> keytool -list -v -keystore keystore.jks > > > sudo keytool -list -v -keystore keystore.jks...
