How do I bypass a proxy for Bitbucket Server

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Purpose

For troubleshooting purposes, it may be required to bypass a proxy by using an additional port to access Bitbucket Server.

This is required when you want to make sure that the problem you are experiencing is not related to a proxy misconfiguration (i.e. git cloning, browsing through specific pages, etc. ).

If you are trying to bypass proxy(ies) in order to create AppLinks that are failing because you suspect that the proxies could be causing this, a more complete set of instructions can be found on:


Solution

Bitbucket Server versions < 5.0

  • Stop Bitbucket Server
  • Add the following lines in $BITBUCKET_HOME/shared/server.xml:

    <Connector executor="tomcatThreadPool"
        port="7995" protocol="HTTP/1.1"
        connectionTimeout="20000" />
  • Start Bitbucket Server
  • Log in using http://<server_ip>:7995
  • Try to reproduce the problem

    • If the problem cannot be reproduced, it is related to the proxy configuration

    • If you can still reproduce the problem, it is not related to the proxy configuration

Bitbucket Server versions >= 5.0

As of Bitbucket Server 5.0, you can't configure any Tomcat connectors directly as the application runs on Spring Boot.

The usual server.xml configuration has been replaced by properties that need to be configured on <Bitbucket Home directory>/shared/bitbucket.properties. Similarly, you can't configure web.xml

  • Stop Bitbucket Server
  • Add the following lines in $BITBUCKET_HOME/shared/bitbucket.properties:

    server.additional-connector.1.port=7995
  • Start Bitbucket Server
  • Log in using http://<server_ip>:7995
  • Try to reproduce the problem

    • If the problem cannot be reproduced, it is related to the proxy configuration

    • If you can still reproduce the problem, it is not related to the proxy configuration

Alternatives - Bitbucket Server 5.0

How to bypass a reverse proxy or SSL in Application Links


GIT operations using SSH

To bypass proxy and clone via SSH on the server directly, it's enough to replace the proxy domain with the Bitbucket hostname instead. For instance, instead of using proxy-domain as the URL, use the hostname bitbucket-hostname:

git clone ssh://git@bitbucket-hostname:7999/te/test.git



Description

This page covers how to bypass a proxy for Bitbucket Server for troubleshooting purposes.

ProductBitbucket



Last modified on Apr 22, 2022

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.