GunBot v13 causing issues logging into Kraken

[kingtaco]

Hi All,  I recently got setup on V13 Starter, trading on kraken.  After getting my bot setup on my local machine, I'm finding that after a few hours I can no longer login to https://www.kraken.com/login, and get a 1020 error from cloudfront, claiming my IP is causing abuse.  If I force my network to get a new public IP, I can login again for a few hours, then get the same issue.  It appears that gunbot is "abusing"(their term, not mine) the login page hence the ban.

api.kraken.com still works, as does trade.kraken.com, but neither of those allows you to access stuff like funding and other account items(e.g. how much til the next fee tier)

Has anyone else experienced this?  I'm likely to upgrade the the GunBot Standard v14 soon, has anyone experience something like this in either version and/or has a work around other than hosting the software at a different IP?

[kingtaco]

To Add: this is krakens help page on the topic: https://support.kraken.com/hc/en-us/articles/360032836911-Cloudflare-errors

[Aitor]

You need to increase your delay. What number? It depends on the exchange and your connection. Start setting it to 20 and check it works fine, then try 18, 16, 14 until you find the lowest amount you can set. Anyway, I think that higher delays are usually better. Personally I get better performace with higher delays (30+), so I wouldn't care too much about getting the lowest delay possible.

[kingtaco]

Thanks.  I also asked my dealer about this, he also thought it was the delay.  it was originally set to 10, and at his suggestion I bumped it up to 12.  I also moved the bot over to AWS so I can't tell if this would have fixed the issue.  He was surprised that a delay of 10 was too low.

[Aitor]

Hi, as I told you, it depends on the exchange. For example many people needs 22+ on Poloniex. Other exchanges allow even 1.