Setting scheme="https" breaks application link from JIRA to Bitbucket

Tony Fontanilla

Unless scheme="https" is set in server.xml, gravatar images are served over http, breaking https.

However, if scheme="https" is set, then the application link between JIRA and Bitbucket is broken on the JIRA side.

When this happens, the following message will be displayed on the JIRA side, even though the Bitbucket side says that they are connected.

"Application 'Bitbucket' seems to be offline. Click here to Relocate."

G__Sylvie_Davies__bit-booster_com_

What's your end-to-end config here?

In my shop I let Apache do the "https" on 443, and use Apache's ProxyPass and ProxyPassReverse directives to route the traffic to Bitbucket Server's tomcat running on its default port 7990.

I had all sorts of problems with my JIRA <--> Bitbucket link initially.  The trick in my case was to let Bitbucket's Tomcat know what was going on in its config (bitbucket-data/shared/server.xml), like so:

<!-- The 5 un-indented lines are the ones I had to
     add to make my JIRA/Bitbucket application link work:
-->
<Connector port="7990" protocol="HTTP/1.1"
           connectionTimeout="20000"
           useBodyEncodingForURI="true"

redirectPort="443"
secure="true"
scheme="https"
proxyName="bitbucket.internal.mycompany.com"
proxyPort="443"

           compression="on"
/>

 

- Regards,

Sylvie Davies

Founder and Software Engineer, bit-booster.com

 

p.s.  be sure to try out my Bit-Booster Commit Graph And More add-on.  It's the best commit graph add-on for Bitbucket Server. Dramatically improves your team's ability to see exactly what's happening in your Git repositories. Don't forget to enable the included Bit-Booster hook to prevent foxtrot merges in master.