BaseUrl healthcheck error - [B cannot be cast to java.lang.string

Question

I have just upgraded to JIRA 7.3.6 to JIRA 7.4.1. JIRA is reporting to me that the Base URL checks are failing however I cannot see where there is a misconfiguration. I cannot make a link from JIRA to Bitbucket and the System Dashboard crashes/appears to be corrupted. My diagnosis is that the former issue is having a knock-on effect to the latter issues.

My setup: JIRA and Bitbucket are integrated with Apache over SSL. The configuration of /etc/httpd/conf.d/ssl.conf is identical to when we were on 7.3.6 and there were no issues like this. The config in {JIRA_install}/conf/server.xml closely reflects the SSL config and is identical to when we were on 7.3.6.

The issues:

In the Support Tools section of JIRA, it is being reported that the Base URL health check is failing. The Base URL is set correctly in General config. Apache SSL and server.xml settings are good from what I can tell. Logs are below.

When initially logging in to JIRA and the user is directed to the System Dashboard by default, an "Error 500" appears with skull and crossbones. The logs from atlassian-jira.log are below. The dashboardTitle var appears to be undefined....

Starting from Bitbucket, I can make a link to JIRA. When it takes me to JIRA to make the reciprocate link, I get the warning "Please enter a valid URL" and there is an UncheckedExecutionException error. Below is the atlassian-jira.log.

Something strange I have noticed is that when I curl https://atlassian-server/jira the output has "Location: /jira/". When I curl https://atlassian-server/bitbucket the output has "Location: https://atlassian-server/bitbucket". The difference in output is ringing alarm bells to me but I can't figure out how to debug this.

Note: I cannot post all the logs at once as Atlassian thinks I am posting spam. Will be updating this post when I can.

stephankn · Answer

I can confirm that for me, having the same symptoms as described above, the following worked:

I replaced a cacert wildcard certificate with a Let's Encrypt one specific for the jira host.

With java trusting the cacert root and all suggested SSL checks passing I have no idea why jira was extra picky, but later on the thealth check was happy and dashboards worked again.

stephankn · Answer

For me it works well once I disable SSL and access jira using HTTP. So it might be something it doesn't like about the certificate. The two test-programs by atlassian are both happy. So not clear yet what is the issue. Maybe it is because it is a wildcard certificate? It won't see the jira hostname in the certificate. But is this really causing issues?

Note: In my case SSL is terminated by apache. Connection to Jira is via AJP.

stephankn · Answer

Hello Anuja,

I have exactly the same symptoms here.

Have you verified to be able to connect to your server as described here:

https://confluence.atlassian.com/jirakb/health-check-jira-base-url-859447384.html

For me it still does not work, despite all SSL checks passing and no duplicate dashboards. Would be great if you could provide some feedback or further ideas on how to narrow the issue down.

Stephan