Bitbucket - 503 Service Unavailable - post upgrade to 5.14

Question

We have recently upgrade our Bitbucket from 4.9.1 to 5.14 and is running behind a reverse proxy.

Our application url is working fine but when i hit the proxy url, i am getting "503 service unavailable". Logs doesnt help much here, as i couldn't trace any.

Any suggestions please.

Thanks,

Bala

Bala_ialcs7 · Answer

Okay. As of now, if we commented out the proxy parameters in bitbucket.properties file helps.

But curious to understand the usage of server.proxy-name and server.proxy-port.

As per the docs given in the below url, it defines the property as reverse proxy parameter, which we used earlier in server.xml file too.

https://confluence.atlassian.com/bitbucketserver/bitbucket-server-config-properties-776640155.html#BitbucketServerconfigproperties-Server

Can Atlassian help me understand the usage of these attributes?

Thanks,

Bala

Bala_ialcs7 · Answer

Thanks we have the proxy settings defined in properties file. We use the same url from official bitbucket docs for migration.

As we are doing an upgrade, we dont see any changes from proxy server end, unless atlassian confirms.

Appreciate your comments.

Julius Davies _GitBoost_com_ · Answer

To me this sounds like your reverse proxy config is not quite right.  Default Bitbucket listens on port 7990.  Did you perhaps change that in your old 4.x install?  If so, you'll need to also change it in your new 5.x instance, but the config for doing that happens in a different file with Bitbucket 5.x.

Bitbucket 5.x doesn't let you set config in the Tomcat server.xml file anymore.  You need to migrate any custom settings you have in server.xml to bitbucket.properties.

More info here in the official Bitbucket docs:

Migrate server.xml customizations to bitbucket.properties

My old answer with some sample values for "bitbucket.properties" might also be useful:

https://community.atlassian.com/t5/Bitbucket-questions/How-to-change-the-bitbucket-base-url/qaq-p/892162

If you're on a linux box "netstat -lnp" can be very useful for figuring out what ports things are listening on.