HTTP Error 502: Bad Gateway when pushing to bitbucket

Question

I have a mercurial repository, when I try to push my changes to bitbucket I suddenly get the error

HTTP Error 502: Bad Gateway

after a long moment of wait (searching changes..)

Any idea? this has had me stumped for two days!

Are other commands like `hg incoming` and `hg pull` working correctly ? — David Levesque, Aug 07 '12 at 14:59

David Levesque · Accepted Answer · 2018-02-27T18:01:17.723

2

Some people report similar issues when trying to push big changesets using the HTTP protocol. Try using SSH instead. You can find instructions for Bitbucket here.

edited Feb 27 '18 at 18:01

answered Aug 07 '12 at 15:09

David Levesque

22,181
8
67
82

I changed my .hg/hgrc with `ssh://hg@bitbucket.org/accountname/reponame/` but I got this remote: `Permission denied (publickey). abandon : no suitable response from remote hg ! ` – Armance Aug 07 '12 at 15:12
Did you configure your public key in Bitbucket ? – David Levesque Aug 07 '12 at 15:14
How do I do that? excuse me I'm new to all this – Armance Aug 07 '12 at 15:14
That link is dead...it would be nice to duplicate the instructions or update the link. – user Feb 27 '18 at 17:04
1

@user Thanks for the heads-up, I've updated the link. – David Levesque Feb 27 '18 at 18:02
That link says you have to enable compression. **Don't** do that. It'll simply not work and to say the error messages are misguiding is an understatement. – Mark Jeronimus Sep 23 '18 at 19:52

HTTP Error 502: Bad Gateway when pushing to bitbucket

1 Answers1

Linked