Bitbucket is running behind an apache proxy and is accessible through the proxy dns name via https.
Howevers, bitbucket does not automatically detect the scheme on how it was accessed (http/https) so it is showing http:// when getting the clone url.
This could be also a cause why creating a branch is failing show (cross site scripting error).
As per documentation, I can update the the base url through the UI under settings section, but that menu does not exists at all.
Referenced documentation: https://confluence.atlassian.com/bitbucketserver055/specifying-the-base-url-for-bitbucket-server-940682822.html
Current UI displaying
How can I manually update the base url from the configuration without the need to configure ssl on bitbucket itself as it is already handle by apache.
Similar to jira, I can specify base url through the administration screen and change it to use https://
Environment:
Have you also edited your server's "bitbucket.properties" file? My own required these lines:
server.secure=true
server.scheme=https
server.proxy-port=443
server.proxy-name=bitbucket.mycompany.com
There's some good documentation here on setting up any Atlassian "server" product to run behind "https" using an Apache reverse-proxy:
Thanks @Julius Davies [bit-booster.com]
Did not saw this in the documentation but will try this out.
server.proxy-port=443
server.proxy-name=bitbucket.mycompany.com
Cross fingers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Julius Davies [bit-booster.com] - this did work. accepted this answer.
server.proxy-port=443
server.proxy-name=bitbucket.mycompany.com
Somehow, I keep on looking on the administrative UI as the documentation said you can change the base url in the settings (just like jira and confluence). But never found that piece. I saw that configuration but it was more pointing to setting ssl on the bitbucket server itself so I did not bother. (e.g. creating cert, apply cert, etc)
But then the moment you posted it, server.proxy-* which I probably miss.
Thanks.
This fix the issue (branching now works on https) all links on the repository (clone repo) is now showing https
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I find Atlassian pretty responsive on these forums during regular business hours (e.g., Monday - Friday).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.