You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi, we are using bitbucket cloud. But since we started using bitbucket we have changed our live site that we deploy to from http to https and none of our edits get deployed now. I get that .How can we fix this to be able to synch our master repository in cloud with the new server. It should be easy , bit we can't figure out how to do it.
Judith at UCD
Welcome to the Bitbucket Cloud community :)
The most common issue customers are experiencing related to authentication is due to the deprecation of GIT username/password in favour of App Passwords on 01/03/2022:
You will need to make use of an App Password for communicating to GIT via HTTPS.
We have documentation for usage of app passwords at the following link:
Essentially, when connecting via *HTTPS* you will use your AppPassword* alongside your username seperated with a ":" character.
Therefore if you are authenticating to GIT over HTTPS to push/pull you will need to update your remote URL's to include the App Password:
git remote set-url origin https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git
The same applies when performing git clone:
git clone https://USERNAME:APP_PASSWORD@bitbucket.org/workspaceID/reposlug.git
I would suggest ensuring also that all stored passwords related to authentication over GIT are cleared from your machine (ie Credential Manager for Windows, Access Keychain for Mac or /etc/shadow folder for Linux).
Hope this helps.
- Ben (Bitbucket Cloud Support)