HTTP Proxy Bitbucket does not display correctly

[Deleted user]

I am building a bitbucket in development server to test for an upgrade. BitBucket version 4.4.1 In production the HTTPS Proxy works. The same configs on my development server does not. There is no header the words and links show up. and in the middle there is the following line. I can get to Bitbucket using teh IP:7990 and it is fine. I have followed the 

https://confluence.atlassian.com/kb/securing-your-atlassian-applications-with-apache-using-ssl-838284349.html

and compared to production.

Oops, you've found a dead link

Use the links at the top to get back.

Any thoughts would be helpful

[Daniel Eads]

Hey Steve,

Getting everything connected with a reverse proxy can be difficult! Typically we see that the server.xml file for the application doesn't have the necessary info to help Tomcat listen for the correct proxy settings that Apache is trying to pass it.

As you upgrade from 4.4, you're going to find that the settings in server.xml are moving to bitbucket.properties to make upgrades more stable (the things like SSL settings would be overwritten during an upgrade in the server.xml file). We've got a page describing this change here.

The settings I'd try to make sure you have set in server.xml (running a diff of this file against your prod version might be a good idea too):

• proxyPort="443"
• proxyName="mycompany.com"
• secure="true"
• scheme="https"

The proxyName field here should match what you've set for this instance in Apache. It's likely different than what you've got in Prod!

You'll also need to make sure that Bitbucket knows its base URL begins with https rather than http. While it doesn't need to be restarted after changing the base URL, it does need to be restarted if any changes were made in the server.xml file.

Let me know how things turn out from here!

Cheers,
Daniel