Its problem at bitbucket's end.
You can check status of their services at http://status.bitbucket.org/
Currently there is HTTPS
outage at bitbucket. see below
You can use SSH
option. I just used SSH
option with sourcetree
.
I received the same error when trying to clone a heroku git repository.
Upon accessing heroku dashboard I saw a warning that the tool was under maintenance, and should come back in a few hours.
Cloning into 'foo-repository'...
remote: ! Heroku has temporarily disabled this feature, please try again shortly. See https://status.heroku.com for current Heroku platform status.
fatal: unable to access 'https://git.heroku.com/foo-repository.git/': The requested URL returned error: 503
If you receive the same error, check the service status
Try disabling all the system wide HTTP and HTTPS proxies:
export http_proxy=""
export https_proxy=""
export HTTP_PROXY=""
export HTTPS_PROXY=""
This problem is not only created by no_proxy
, because it created by git server down
issue also.
So When happening this issue first you open and check gitlab in browser.
And check if It shows any error like "503 An internal server error occured".
.
The gitlab shows "503"
page, this issue create by gitlab server down not in your system.
So you wait some time until the server going up and continue your work.
A 50X error is an internal server error. There's nothing wrong on your end, but something's up on the server's end.
http://www.checkupdown.com/status/E503.html
The Web server (running the Web site) is currently unable to handle the HTTP request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay.
Just be patient and wait. :-)
here you can see the latest updated status form their website
if Git via HTTPS
status is Major Outage
, you will not be able to pull/push, let this status to get green
HTTP Error 503 - Service unavailable
The solution:
error : The requested URL returned error : 503 while Accessing
The error might be resolved by deleting the existing git folder.
As in "CocoaPods - pod setup http request failed", a 503 error on accessing (cloning) a public repository is likely to be the result of a GitHub glitch (availability issue)
Retrying later usually works.
It was the service issue from the git. The site will be under maintenance. Please try once after the maintenance work is done.
Every one please avoid modifying post buffer and advising it to others. It may help in some cases but it breaks others. If you have modified your post buffer for pushing your large project. Undo it using following command.
git config --global --unset http.postBuffer
git config --local --unset http.postBuffer
I modified my post buffer to fix one of the issues I had with git but it was the reason for my future problems with git.
Had the same error while using SourceTree connected to BitBucket repository.
When navigating to repository url on bitbucket.org the warning message appeared:
This repository is in read-only mode. You caught us doing some quick maintenance.
After around 2 hours repository was accessible again.
You can check status and uptime of bitbucket here: http://status.bitbucket.org/
Source: Stackoverflow.com