502 on push over HTTPS

Hi,

We are seeing push errors occuing with very little information to give to our users. This occurs on save in CloudCannon and is being hit quite often. Are there any flags on my end that I could configure to get less of these? Is this a known issue?

Error: Command failed: /usr/bin/git push origin master -v
Pushing to ...
POST git-receive-pack (3231 bytes)
error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 Bad Gateway
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

I’d appreciate any help on this issue. Let me know if you need any additional information.

Cheers,
George

Hi George,
Sorry for the extremely delayed response. Has this problem persisted for you?

ERIC HENRY
Development Team Lead, Bitbucket Cloud

Hi Ehenry,
I am getting same error.

C:\bitbucket-repo>git push
Counting objects: 50, done.
Delta compression using up to 8 threads.
Compressing objects: 100% (50/50), done.
Writing objects: 100% (50/50), 9.04 KiB | 771.00 KiB/s, done.
Total 50 (delta 39), reused 0 (delta 0)
error: RPC failed; HTTP 502 curl 22 The requested URL returned error: 502 Proxy Error
fatal: The remote end hung up unexpectedly
fatal: The remote end hung up unexpectedly
Everything up-to-date

can you please help to check this?

@ashishghone
This is likely due to a performance issue we had this morning.

ERIC HENRY
Development Team Lead, Bitbucket Cloud

Yes… Its working now… Thanks :slight_smile: