Errors - user agent required, invalid api key & how to preload ticker data

[MrAdamo]

I saw this error while checking the log and have no idea what it is about.

-ERROR- 13/01/2021 23:01:43 - BTC-EUR - invalid web status code 400
{"message":"User-Agent header is required."}

Was the bot attempting to trade and failed?

[mr-highball]

@MrAdamo if you uncheck "info" & "warning" but check "error" for the logging and have the bot run, does this error message keep repeating? the user-agent is just a piece of information passed in each web call that identifies "what" is communicating with the other server (in this case coinbase server)
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

in addition to my previous question about logging can you answer below:
are you running in sandbox / prod?
do you have Key/Secret/Passphrase filled out correctly on the authenticator tab?
can you verify that no orders were placed on coinbase?

[mr-highball]

you can "multi select" ticker files to load either by holding CTRL + clicking or by doing a drag selection

so no need for you to merge them your self. so when you stop the bot for whatever reason you can just select as many recent files as your strategy needs (probably the last 3 or 4 files).

A side note to that, the simulator actually can do a decimate & merge & save to a single file for you (in the case you wanted to simulate with newer data and skip having to decimate)

you also do not need to keep info checked, it's just there to get a full picture of what's going on, but definitely not necessary

[MrAdamo]

The same error appeared again:
-ERROR- 15/01/2021 13:53:44 - BTC-EUR - invalid web status code 400
{"message":"User-Agent header is required."}
-ERROR- 15/01/2021 14:31:58 - BTC-EUR - invalid web status code 400
{"message":"User-Agent header is required."}

And also other errors on other instances of the bot I have running. Each bot has it's own separate folder.
-ERROR- 15/01/2021 13:31:15 - ETH-EUR - invalid web status code -3
The bot above has been collecting ETH ticker files. With 0 fund and a valid API key.

-ERROR- 15/01/2021 14:11:00 - TGDAXOrderManagerImpl::Place::an error occurrred [error]:invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:11:00 - TGDAXBobberStrategyImpl::OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:11:00 - OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:11:01 - TGDAXOrderManagerImpl::Place::an error occurrred [error]:invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:11:01 - TGDAXBobberStrategyImpl::OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:11:01 - OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:12:00 - TGDAXOrderManagerImpl::Place::an error occurrred [error]:invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:12:00 - TGDAXBobberStrategyImpl::OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:12:00 - OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:12:01 - TGDAXOrderManagerImpl::Place::an error occurrred [error]:invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:12:01 - TGDAXBobberStrategyImpl::OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:12:01 - OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:14:28 - TGDAXOrderManagerImpl::Place::an error occurrred [error]:invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:14:28 - TGDAXBobberStrategyImpl::OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:14:28 - OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:14:30 - TGDAXOrderManagerImpl::Place::an error occurrred [error]:invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:14:30 - TGDAXBobberStrategyImpl::OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
-ERROR- 15/01/2021 14:14:30 - OpenPosition::invalid web status code 401
{"message":"Invalid API Key"}
While this bot has been running in sandbox mode with sandbox put as Key/Secret/Passphrase in all the API key setting like you explained in your Software Overview Wiki.

[mr-highball]

so the "invalid api key" message is coming straight from coinbase, so I'm thinking one of the three (key/secret/passphrase) is off OR that the api key does not have the "TRADE" permission. Since it's a sandbox key it also has to be made on the sandbox url

• https://public.sandbox.pro.coinbase.com/ (login here and make sure funds are there and create the key here)

AND you have to "fund" the sandbox account (same process has funding regular account with the deposit button, but instead of linking a bank account it just lets you type in how much money you have).
I'd recommend just blowing away this key and just re-creating following their steps (make sure you copy the secret once it's shown because it's only shown once, and give it TRADE permission)

• https://help.coinbase.com/en/pro/other-topics/api/how-do-i-create-an-api-key-for-coinbase-pro
• https://docs.pro.coinbase.com/#generating-an-api-key

I'm still uncertain on the user agent error since I have not received that message before with valid creds, but the tester application I linked in the previous comment can be used to do the preliminary checking that your key is good and that it can place a sandbox order.

Lastly for the "invalid web status code -3" if it doesn't happen too often this may be just fine and a problem with communication to their api (sometimes they have outages or timeouts occur). I'd recommend if your running multiple instances (which is no problem I do it too) to offset the poll interval by a second or so (if one bot is set to 1500 set the second one to 2500 or 3000 msecs). This is to avoid any issues hitting the ticker endpoint since coinbase does "throttle" the amount of requests per second
https://docs.pro.coinbase.com/#rate-limits

down the road I'll probably give the option to connect to their websocket feed which doesn't have the rate limits, but I just haven't gotten to it.

[mr-highball]

one more thing I should mention, just make sure the "sandbox" mode is checked on the authenticator tab of the bot

[mr-highball]

have not heard back, hope you were able to resolve the issues. if not I'd recommend trying the latest v1.0.1 release.