nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

URL Redirect WITHOUT Proxy

Paul Klassen

I have the following issue...
A customer has a bitbucket server and moved to another domain this year.
Of coure he'd like to use a new subdomain for bitbucket.

let's say his old domain was old.red-company.com/bitbucket

and the new he'd like to use is new.blue-company.com

Although I changed and edited the configuration on the Proxy Server, the domain new.blue-company.com ALWAYS redirects me to old.red-company.com/bitbucket.
We also checked the Domain settings at their hoster because we though it might be a redirect there, but no, nothing.

Then I noticed that if I try to open bitbucket with <internalserverip>:7990/bitbucket

it is redirecting over and over again to old.red-company.com/bitbucket

I have no clue what this might be and I assume it's some kind of configuration on the bitbucket server itself. Any ideas or solutions for this?

Accepted answers

All comments

Alexis Robert

Hello,

can you check that you have correctly set the Base URL as shown here: https://confluence.atlassian.com/bitbucketserver/specifying-the-base-url-for-bitbucket-server-776640392.html

It should work fine if you have new.blue-company.com set here.

Let me know if it works,

Cheers,

-- Alexis

Paul Klassen

Hi Alex,

thank you for your reply!

Yes, I already checked this an the new URL is already set there, but it still redirects to the old one.

Alexis Robert

Hi Paul,

can you check with Chrome devtools what is happening in terms of redirections when you go to new.blue-company.com ? You can access this tool simply by Right-Click -> Inspect and then select Network tab and load new.blue-company.com

Cheers,

--Alexis

Paul Klassen

Hi Alexis,

sorry for misspelling your name in my first reply.

Since I don't use Chrome I tried this with Firefox.
I tried the the old address, the new and the IP of the Bitbucket Server itself, this is what I got.

When I access new.blue-company.com:
1. new.blue-company.com connects to the external IP of my reverse Proxy
2. reverse proxy answers with "Location: https://old.red-company.com/bitbucket/projects"

When I access old.red-company.com/bitbucket:
1. old.red-company.com/bitbucket connects to the external IP of my reverse Proxy
2. reverse proxy answers with "Location: https://old.red-company.com/bitbucket/"

When I access <internalIP>:7990/bitbucket:
1. <internalIP>:7990/bitbucket connects to the internal IP of the Bitbucket server itself
2. Bitbucket server answers with "Location: https://old.red-company.com/bitbucket/"

I hope this Info helps. If not, let me know what exactly you have to know.

Have a nice day,
Paul

Martin Liu

Hi Paul,

You may need to check the file shared/server.xml or shared/bitbucket.properties

Martin

Ergo Loorits

I'm experiencing the exact same issue right now

seems like something is cached somewhere even though all the configs and properties are set correctly as suggested in the docs

how to prevent this 302?

Ergo Loorits

I found my issue:

SERVER_PROXY_NAME environment variable was still set to old hostname (as I'm using Docker)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

bitbucket