Page 1 of 1

Bitbucket, & Foundry

Posted: Sun Mar 08, 2015 5:47 pm
by admin
This forum is specifically for Bitbucket issues, questions, support. hosts its repositories at, an Atlassian company which produces the software our Foundry uses to manage software development. Foundry synchronizes with Bitbucket. Atlassian also produces SourceTree, a free graphical Git & Mercurial client for Windows or Mac anyone can use to contribute to development.

There is a new resource link to Bitbucket in the section of the forum index. It uses the DNS CNAME feature to allow Bitbucket to appear as a subdomain of i.e.,

Please be aware that Bitbucket has the following warnings when using their service on the domain:
Bitbucket wrote:Using a CNAME with Bitbucket will result in unencrypted http:// (not the https:// which Bitbucket uses) communication between your users and the Bitbucket website. This means passwords and other potentially sensitive data will be sent in clear text.
Bitbucket follows up with this recommendation:
Bitbucket wrote:Please note that accessing a Bitbucket account configured with a custom domain over HTTPS may result in security warnings from your browser.

The Bitbucket service can only serve one SSL certificate, and that certificate can only be associated with the domain. When you access a CNAME over HTTPS, your browser will see that the certificate's domain doesn't match the address you've visited and presents a warning message. For this reason, we allow non-secure HTTP access to CNAMEs. However, if you don't mind the certificate warnings and you'd prefer to access your CNAME over an encrypted session, you can still use HTTPS.

For cloning, pushing, and pulling to repositories on CNAMEs, we recommend connecting directly to over HTTPS or SSH to ensure your password is transmitted securely.

Re: Bitbucket, & Foundry

Posted: Tue Jun 09, 2015 6:22 pm
by admin
Bitbucket is terminating the CNAME service effective July 1st. So... nevermind.

Re: Bitbucket, & Foundry

Posted: Thu Jan 19, 2017 10:30 pm
by admin
In the ongoing subdomain saga at Bitbucket, we got this today:
Atlassian wrote:We're emailing you because you host a static website using Bitbucket. You can now access your site using - we've added SSL for your security. No action is required on your part.

Visitors to will be automatically redirected to as of January 23rd. After March 1st, 2017, requests to will no longer be supported. HTTPS is required to access

Please update any links or references to to instead point to
This is of little to no significance to anyone, including It's just posted here for completeness.