Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error occurred in getFees method. #13

Open
akjroller opened this issue Mar 7, 2021 · 2 comments
Open

Error occurred in getFees method. #13

akjroller opened this issue Mar 7, 2021 · 2 comments

Comments

@akjroller
Copy link

akjroller commented Mar 7, 2021

After following all steps in the set up of this bot I am getting an error when trying to run the bot.
I am using windows 10 installed newest version of NodeJS and Git.
Ran npm install from within the repo directory at the root .
Created the .env file with all required components
Uncommented out the lines for running bot on coinbase pro sandbox and commented out the lines for running the bot on the live coinbase pro

Am I missing something?

{"level":50,"time":1615149540237,"pid":2676,"hostname":"Awakengaming83","message":"Error occurred in getFees method. Number of attempts: 3","errorMsg":{},"err":{"message":"
Request failed with status code 401","stack":"Error: Request failed with status code 401\n at createError (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-Cry
pFinder-master\node_modules\axios\lib\core\createError.js:16:15)\n at settle (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFinder-master\node_mod
ules\axios\lib\core\settle.js:17:12)\n at IncomingMessage.handleStreamEnd (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFinder-master\node_modules
\axios\lib\adapters\http.js:244:11)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAnd
Rejections (internal/process/task_queues.js:80:21)","config":{"url":"https://api-public.sandbox.pro.coinbase.com/fees","method":"get","headers":{"Accept":"application/json,
text/plain, /","CB-ACCESS-KEY":"","CB-ACCESS-SIGN":"upelCSMF4ryaOg5PbMcuQiJjphM7SvIo2OSIKahclQ4=","CB-ACCESS-TIMESTAMP":1615149540.081,
"CB-ACCESS-PASSPHRASE":"","User-Agent":"axios/0.20.0"},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHead
erName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1}}}
{"level":50,"time":1615149540239,"pid":2676,"hostname":"Awakengaming83","message":"Error occurred in getFees method.","errorMsg":{},"err":{"message":"Request failed with st
atus code 401","stack":"Error: Request failed with status code 401\n at createError (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFinder-master\node_m
odules\axios\lib\core\createError.js:16:15)\n at settle (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFinder-master\node_modules\axios\lib\core
\settle.js:17:12)\n at IncomingMessage.handleStreamEnd (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFinder-master\node_modules\axios\lib\adapters
\http.js:244:11)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n at processTicksAndRejections (internal/p
rocess/task_queues.js:80:21)","config":{"url":"https://api-public.sandbox.pro.coinbase.com/fees","method":"get","headers":{"Accept":"application/json, text/plain, /","CB-
ACCESS-KEY":"","CB-ACCESS-SIGN":"upelCSMF4ryaOg5PbMcuQiJjphM7SvIo2OSIKahclQ4=","CB-ACCESS-TIMESTAMP":1615149540.081,"CB-ACCESS-PASSPHRASE"
:"","User-Agent":"axios/0.20.0"},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XSRF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN"
,"maxContentLength":-1,"maxBodyLength":-1}}}
{"level":50,"time":1615149540239,"pid":2676,"hostname":"Awakengaming83","message":"Error occurred in bot, shutting down. Check the logs for more information.","errorMsg":{}
,"err":{"message":"Request failed with status code 401","stack":"Error: Request failed with status code 401\n at createError (C:\Users\akjro\Desktop\Coinbase-Pro-Cry
pto-Trading-Bot-CrypFinder-master\node_modules\axios\lib\core\createError.js:16:15)\n at settle (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFind
er-master\node_modules\axios\lib\core\settle.js:17:12)\n at IncomingMessage.handleStreamEnd (C:\Users\akjro\Desktop\Coinbase-Pro-Crypto-Trading-Bot-CrypFinder-m
aster\node_modules\axios\lib\adapters\http.js:244:11)\n at IncomingMessage.emit (events.js:327:22)\n at endReadableNT (internal/streams/readable.js:1327:12)\n
at processTicksAndRejections (internal/process/task_queues.js:80:21)","config":{"url":"https://api-public.sandbox.pro.coinbase.com/fees","method":"get","headers":{"Accept"
:"application/json, text/plain, /","CB-ACCESS-KEY":"","CB-ACCESS-SIGN":"upelCSMF4ryaOg5PbMcuQiJjphM7SvIo2OSIKahclQ4=","CB-ACCESS-TIMESTA
MP":1615149540.081,"CB-ACCESS-PASSPHRASE":"","User-Agent":"axios/0.20.0"},"transformRequest":[null],"transformResponse":[null],"timeout":0,"xsrfCookieName":"XS
RF-TOKEN","xsrfHeaderName":"X-XSRF-TOKEN","maxContentLength":-1,"maxBodyLength":-1}}}

@LeviathanLevi
Copy link
Owner

LeviathanLevi commented Mar 7, 2021

Hey akjroller, getFees is the very first API method call and it returned 401 which means it isn't happy with your API key it thinks it's invalid for some reason.
image
Make sure that if you did specify an IP whitelist your correct public IP is listed (I think you can also leave it blank to allow all IPs). Make sure it has view/trade/transfer permissions. Double check that the API key you gave it is in the correct environment, that is to say if you're trading in the sandbox the API key was made in the sandbox and same for the actual site. Also check the tradingProfileName, it needs to match the name of the profile you made exactly and it needs to be the profile that has the API key created in it, my guess is your issue might be there.

Hopefully that helps

@saiaman
Copy link

saiaman commented May 19, 2021

.env file not loaded, same here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants