Open tomhatzer opened 7 years ago
+1
Using 'demo-api.hitbtc.com' as address for the ws endpoints and having created a full-access API key via the demo webui, I'm receiving the same error.
'hitbtc.com' API dashboard shows correct "Last use" time for the API and 'tribeca' logs show a HTTP 200 OK. I've tried 'wss' for the demo-api websocket endpoints, but it didn't work either.
I'm using the latest code available (ee50c64) and I have been diggin on it, but I couldn't find any reasonable reason for the problem of receiving a 200; Until I sniffed the requests (the showing API key, it's already revoked).
It seems that the api endpoint on port 80 is not implementing GET on '/' but is returning 200. I don't know if this is something expected in someway from part of 'hitbtc.com', I haven't tried its API natively.
My two cents!
Hi everybody!
I'm currently trying to get tribeca up and running on my server. When starting tribeca using forever, I'm receiving the error message below. API Key and secret were generated a few minutes ago.
I replaced all unnecessary data with <censored>, I hope that's ok. I triple checked if the api key and secret match the details from the api key website, and they do.
Do you possibly know, what's wrong?
Thanks and best wishes Tom
Exception (the last few lines are the ones with the error messages):