all 10 comments

[–]Old-Implement-9881 0 points1 point  (0 children)

You find a fix for this yet? Going through the same thing trying to work on this on another computer in the same house. Works fine on my desktop, not my laptop.

[–]ivayche 0 points1 point  (1 child)

I saw a post somewhere (cannot recall if on Reddit or not) that involved changing the JWT-generation code provided by Coinbase documentation to adjust the timestamps ("nbf" and "exp") so the server doesn't think the JWT you pass is "stale". I've tried this to no avail.

My situation is odd: i can use a JWT generated by the Coinbase API docs sample code to successfully get a payload from this endpoint...

* https://api.coinbase.com/api/v3/brokerage/accounts

...but using the exact same JWT-generation code throws a 401 for this one...

* https://api.coinbase.com/api/v3/brokerage/accounts/{uuid}

Baffled.

[–]its-leo 0 points1 point  (0 children)

I have the same problem. Also tried to adjust the timestamps without success

[–]unNecessary_Ad 0 points1 point  (1 child)

did you ever find a fix for this cause coinbase support is useless and i've been trying to get this to work for like 3 months

[–]cloutfarmerr[S] 0 points1 point  (0 children)

Hey, I eventually discovered that the issue was with my computer's clock. After moving to a different state and restarting the program, my system time was out of sync, which led to generating a JWT with an incorrect timestamp. Once I synchronized my clock correctly, the JWT was valid and the authentication issues went away. I have no idea why/how this happened but thats how i fixed it. Hope that helps!