Health check problem after upgrade

Boris February 28, 2017

Hello,

My colleague upgraded our Jira and Confluence from v7.1.8 to 7.3.1.
Now we have the following problem during our Health check:
"Checks if JIRA is able to access itself through the configured Base URL."

We have this configured in /etc/httpd/conf.d/ssl.conf:

<VirtualHost *:443>
    ServerAdmin networking@worldsupport.info
    ServerName jira.corp.int

    SSLEngine On
    SSLCertificateFile /etc/httpd/certs/jira.corp.int.crt
    SSLCertificateKeyFile /etc/httpd/certs/jira.corp.int.key

    SSLProxyEngine on
    ProxyPass / http://localhost:8080/ connectiontimeout=1200 timeout=1200
    ProxyPassReverse / http://localhost:8080/

    ProxyPreserveHost On
    ProxyTimeout 1200

    ProxyRequests Off
    ProxyVia Off
    ErrorLog /var/log/httpd/jira.corp.int/ssl-error.log

    LogLevel warn

    CustomLog /var/log/httpd/jira.corp.int/ssl-access.log combined
    ServerSignature On

    RequestHeader unset Proxy early
    </VirtualHost>



Also, we have Connector configured in our cat /opt/atlassian/jira/conf/server.xml:

<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"
    ProxyName="jira.corp.int"
    />


At this point the integration between Jira and Confluence is OK, but the Health check is not.

If we add to the connector those lines:

scheme="https"
    proxyName="jira.corp.int"
    proxyPort="443"

the integration between Jira and Confluence breaks down, but the Health check of Jira is OK.

 

Do you have any idea what seems to be the root cause of the problem?

1 answer

0 votes
Niclas Sandstroem
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 5, 2017

Without knowing the full story of your configuration or setup. But I would guess you run JIRA and Confluence on the same server without context path. If you can run JIRA and Confluence app links without proxy this should be possible by following this KB.

https://confluence.atlassian.com/kb/how-to-bypass-a-reverse-proxy-or-ssl-in-application-links-719095724.html

Please review the existing https://confluence.atlassian.com/jirakb/health-check-jira-base-url-859447384.html suggestions.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events