Hi.
First of all, why I do have TWO of the same App Free Cloud in my account.
But most of all, git pushing stopped working since Easter, I tried deleting the ssh key I was using, sticking in another one, but still:
Unauthorized (for both, the former worked until Easter)
But the funny story is:
ssh -T git@bitbucket.org
authenticated via ssh key.
You can use git to connect to Bitbucket. Shell access is disabled
If free and private means to be abandoned with the service and no support at all to say "No error message why it suddenly stopped working", then "no thanks", I prefer paying few bucks to GitHub and have support in such events.
Thanks for having me got lost and not able to update the web site via git.
Hi Maximarc,
I have clicked the request assistance button, so Atlassian support can see this post and look to help you out.
I hope this information helps.
Regards,
Kristian
Any news on that? Should we roll our keys or anything else to solve this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No news on that. The only news is that I joined GitHub, where private repos are now FREE. And my same keys worked straight away, without needing to fight to get authorized by the ssh-agent on board.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @mazimarc
I'd like to confirm that private repo's are also free in Bitbucket Cloud, the error you're seeing is GIT specific and relates to an issue with your SSH key (likely with how its been loaded into the ssh agent).
If you decide to return to Bitbucket - we have an article for troubleshooting SSH issues that can be found here:
Kind Regards,
- Ben (Bitbucket Cloud Support)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think so, as exactly the same KEY and the same AGENT, successfully connected to GitHub just after I firstly posted this.
I don't know what YOU DID...... not me.
Anyway, thanks for your time. It was pity it had worked since, and suddenly stopped, without me doing anything special to deserve an outage on your end.
And however, this:
ssh -T git@bitbucket.org
authenticated via ssh key.
was giving a green light, but pushing not.
Cheers
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.