Cosmos-SDK API (Osmosis, Kava, Crypto.org): api returned 502 bad gateway (502), try again later
complete
M
Merlot Swift
marked this post as
complete
This issue has now been fixed. Cosmos, Kava, Osmo, CRO, SCRT wallets can all be synced normally now
G
Glamorous Gerbil
Merlot Swift: YAAAASSS!!!!!
D
Dawn pink Caterpillar
Merlot Swift: Yes, I don't get the error message anymore but I don't see my latest transactions on my KAVA wallet. It may be syncing but it is not grabbing the latest transaction, they don't show up in Koinly's transactions.
M
Merlot Swift
Dawn pink Caterpillar:
That is very interesting...
Has the wallet finished syncing and still no transactions?
If so, could you try to sync the wallet from the beginning, as described here:
D
Dawn pink Caterpillar
Merlot Swift: I did exactly as the article instructed and still does not show the latest transactions. I don't think the api is grabbing the info from the blockchain.
M
Merlot Swift
Dawn pink Caterpillar: Ok, thank you for trying that.
I did some digging and it turns out that this fix will also add an automatic "Start sync from" date to your API settings. This is done to prevent potential duplicate transactions from importing unexpectedly.
The article above does contain a paragraph at the bottom on how to remove this date but it's actually much easier to just delete the wallet and recreate it. This will resync the entire transaction history and include the missing transactions.
T
Tremendous Mole
Merlot Swift: in my case it synced only today's transaction on CDC. But all the ones that occurred since the syncing broke are missing (feb 18 - jan 6)
D
Dawn pink Caterpillar
Merlot Swift: YES, your are definitely right. I just changed the start date from what it was set to: 02/06/2023 to ---> 01/01/2023, and voila, IT WORKED! Just click on the: Edit API settings and changed the "Start import from" date. Thank you.
M
Merlot Swift
Merged in a post:
Kava wallet API addresses not syncing
L
Lichen Iguana
Error message shows
api returned 502 bad gateway (502), try again later
This error has been showing for at least a month as far as I know.
Similar error on Crypto.Org wallet API (this is already reported separately by another user)
K
Kumquat Basilisk
Merged in a post:
Crypto.org chain sync doesn't work anymore
T
Tremendous Mole
Gives error 502 bad gateway when syncing an already existing wallet or error 422 when adding a new one.
Y
Yacht club Chicken
same error message when trying to sync Osmosis and Cosmos wallets
S
Shiny Meerkat
I also received a
heads-up
from CDC who said of Koinly API:"It looks like their API is pointing to an incorrect endpoint or searching incorrectly"
S
Shiny Meerkat
Reported to support on 27 Jan 2023, was advised it is now with engineers but not showing as scheduled to be fixed! I suggest chasing.
This post was marked as
in progress
Konstantin Kanyuka
Merged in a post:
Secret API: API returned 502 bad gateway (502), try again later
K
Kumquat Basilisk
156 wallets effected
Wallet ID
: DDB1ECA9E7EF19A61D96CEF69C20AFA5User
: joshl.cross@gmail.comTransactions seem to be imported but the error unknown
Konstantin Kanyuka
Merged in a post:
Crypto.org API Error: api returned 502 bad gateway (502)
T
Tangerine Sparrow
Wallets affected in last 24hr: 294
example address: cro14tjm3syuj2jarguls7wev4k0wk3d8uaklj0k93
email: dougl888@hotmail.com
Temporary workaround: CSV files
Photo Viewer
View photos in a modal
Konstantin Kanyuka
marked this post as
planned
Load More
→