Setup SSL on existing non-SSL server

[Paul Pelland]

Running Ubuntu and 9.4 that ran on port 8080.  Wanted to get to 8443/443.  The .jks file appears just file, but somewhere along the way I lost browser connectivity and the logs aren't very happy.  My thoughts are that somehow one of the .xml files got piddled on (server/db_config/web).

Here are some errors I see:

catalina.out

2023-11-24 07:49:25,612+0000 JIRA-Bootstrap ERROR [c.a.d.c.p.c.algorithm.serialization.SerializationFile] Couldn't read file needed for encryption/decryption. Tried to read file under: /var/atlassian/application-data/jira/keys/javax.crypto.spec.SecretKeySpec_1652407668392
2023-11-24 07:49:25,616+0000 JIRA-Bootstrap ERROR [c.a.d.c.p.ciphers.algorithm.AlgorithmCipher] Runtime Exception thrown when decrypting: DecryptionParameters{sealedObjectFilePath='null', keyFilePath='/var/atlassian/application-data/jira/keys/javax.crypto.spec.SecretKeySpec_1652407668392', serializedSealedObject='rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAASBBAkhH4Sy7lwq+vX35fUykxCdXEAfgAEAAAAUCdWFbY7RQz2SF7QpWFEhIrH4F2IxJq3aqyxiGfjegqXMByEdqr7wMi6CBYR+WtPr9nAJNqVP+xzFV2VhHTRYgSzTcvdhrFrPnQSpSXnjkMSdAADQUVTdAAUQUVTL0NCQy9QS0NTNVBhZGRpbmc='}
2023-11-24 07:50:01,099+0000 Caesium-1-4 ERROR [c.a.jira.startup.IndexRecoveryLauncher] [INDEX-FIXER] Issue index is out of date with the database (issue_version) by more than 48 hours. Automatic recovery will not be attempted

atlassian-jira.log.3:2023-11-21 06:05:35,121+0000 JIRA-Bootstrap ERROR [c.a.d.c.p.c.algorithm.serialization.SerializationFile] Couldn't read file needed for encryption/decryption. Tried to read file under: /var/atlassian/application-data/jira/keys/javax.crypto.spec.SecretKeySpec_1652407668392
atlassian-jira.log.3:2023-11-21 06:05:35,147+0000 JIRA-Bootstrap ERROR [c.a.d.c.p.ciphers.algorithm.AlgorithmCipher] Runtime Exception thrown when decrypting: DecryptionParameters{sealedObjectFilePath='null', keyFilePath='/var/atlassian/application-data/jira/keys/javax.crypto.spec.SecretKeySpec_1652407668392', serializedSealedObject='rO0ABXNyABlqYXZheC5jcnlwdG8uU2VhbGVkT2JqZWN0PjY9psO3VHACAARbAA1lbmNvZGVkUGFyYW1zdAACW0JbABBlbmNyeXB0ZWRDb250ZW50cQB+AAFMAAlwYXJhbXNBbGd0ABJMamF2YS9sYW5nL1N0cmluZztMAAdzZWFsQWxncQB+AAJ4cHVyAAJbQqzzF/gGCFTgAgAAeHAAAAASBBAkhH4Sy7lwq+vX35fUykxCdXEAfgAEAAAAUCdWFbY7RQz2SF7QpWFEhIrH4F2IxJq3aqyxiGfjegqXMByEdqr7wMi6CBYR+WtPr9nAJNqVP+xzFV2VhHTRYgSzTcvdhrFrPnQSpSXnjkMSdAADQUVTdAAUQUVTL0NCQy9QS0NTNVBhZGRpbmc='}
atlassian-jira.log.3:2023-11-21 06:05:35,151+0000 JIRA-Bootstrap ERROR [c.a.crowd.crypto.DbConfigPasswordCipherEncryptor] Error during decryption
atlassian-jira.log.3:2023-11-21 06:06:07,955+0000 JIRA-Bootstrap ERROR [c.a.w.plugin.module.WebHookRegistry] There was an error while reading existing WebHooks events
atlassian-jira.log.3:2023-11-21 06:06:07,956+0000 JIRA-Bootstrap ERROR [c.a.event.internal.AsynchronousAbleEventDispatcher] There was an exception thrown trying to dispatch event [com.atlassian.greenhopper.analytics.JiraAgileStartAnalyticEvent@261ab0b8] from the invoker [com.atlassian.event.internal.ComparableListenerInvoker@307a67ff]
atlassian-jira.log.3:2023-11-21 06:06:08,110+0000 analyticsEventProcessor:thread-1 ERROR anonymous [c.a.j.cache.request.RequestCacheRecorderImpl] Invalid use of RequestCache by thread: analyticsEventProcessor:thread.Incorrect usage of JIRA API. You can only create/use: RequestCacheImpl inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtil for details. This message will be logged once per thread. This ERROR should be fixed on the caller side (check the stack-trace or thread-name) as it is causing inconsistent data.
atlassian-jira.log.3:2023-11-21 06:06:10,720+0000 main ERROR [c.a.j.cache.request.RequestCacheRecorderImpl] Invalid use of RequestCache by thread: main.Incorrect usage of JIRA API. You can only create/use: RequestCacheImpl inside a context (request or Jira-Thread-Local). Check: JiraThreadLocalUtil for details. This message will be logged once per thread. This ERROR should be fixed on the caller side (check the stack-trace or thread-name) as it is causing inconsistent data.

Name: Gadget feed URL
NodeId: null
Is healthy: false
Failure reason: Jira is not able to access itself through the Gadget feed URL. This is necessary so that dashboard gadge
ts can be generated successfully. Please verify the current Base URL and if necessary, review your network configuration
s to resolve the problem.
Severity: WARNINGAdditional links: []

Any help/direction/debug would be greatly appreciated as I am not getting very far.  Thanks in advance.

Paul

[Metin Savignano]

Looks like you're trying to configure Jira to do the SSL? I recommend to set up an HTTPS reverse proxy instead. In my experience, that's the easier approach.

We run Jira in Docker together with jwilder/nginx-proxy, which is easy to set up and works like a charm.