nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Base URL for gadgets problem

Daniel John_lcnnki

Has anyone else upgraded from 6.4.x to 7.4.1 and received an health check error about "Base URL for gadgets"?? what does this mean?

my base URL is correct from what i gather.

https://jira.MYSERVERNAME.com/jira

the context path is set to '/jira' on server.xml.

anyone else experience this?

Accepted answers

All comments

Nic Brough -Adaptavist-

It's a bit more sensitive to proxy misconfiguration in JIRA 7 - what did you add for scheme, proxy and port on the end of the connector?

Daniel John_lcnnki

Here is the snippet from my configuration:
<Service name="Catalina">

<Connector port="8080"

                   maxThreads="150"
                   minSpareThreads="25"
                   connectionTimeout="20000"
                   enableLookups="false"
                   maxHttpHeaderSize="8192"
                   protocol="HTTP/1.1"
                   useBodyEncodingForURI="true"
                   redirectPort="8443"
                   acceptCount="100"
                   disableUploadTimeout="true"
                   bindOnInit="false"/>

<Connector port="28080"

                   maxThreads="150"
                   minSpareThreads="25"
                   connectionTimeout="20000"
                   scheme="https"
                   proxyName="jira.jirahost.com" | this matches the base URL on the jira administration page on my installation
                   proxyPort="443"
                   secure="true"
                   enableLookups="false"
                   maxHttpHeaderSize="8192"
                   protocol="HTTP/1.1"
                   useBodyEncodingForURI="true"
                   redirectPort="8443"
                   acceptCount="100"
                   disableUploadTimeout="true"/>

Daniel John_lcnnki

should add, i inherited this from someone else. im not too familiar with tomcat settings/proxys

Nic Brough -Adaptavist-

Bother

scheme="https"
proxyName="jira.jirahost.com"
proxyPort="443"
secure="true"

Is the bit I was looking for and it looks fine.

Next question is what the proxy is set up to do - nginx, Apache or something else?

Daniel John_lcnnki

Ended up being this fix:

"-Djsse.enableSNIExtension=false" setting to the Java arguments in <JIRA_install>/bin/setenv.sh

straight from atlassian.

Melvin Arroyo

Daniel,

Where exactly did you add that code? i'm lookin in the setenv.sh, but don't know where to make the changes,

Daniel John_lcnnki

on my file, its near the top. you can place it anywhere in the file i'd imagine. this is just a sane way of doing it.

#
# Occasionally Atlassian Support may recommend that you set some specific JVM arguments. You can use this variable below to do that.
#
JVM_SUPPORT_RECOMMENDED_ARGS="-Djsse.enableSNIExtension=false"

#
# The following 2 settings control the minimum and maximum given to the JIRA Java virtual machine. In larger JIRA instances, the maximum amount will need to be increased.