You are being rate limited about exchange-proxy HOT 5 CLOSED

Hello,

Actually, the proxy could violate kucoin filtering rules, but only on startup, when it's trying to prefetch candles before starts receiving them over WebSocket. When 429 occurs, the proxy forwards the response transparently to freqtrade to make it fetched again.

Regarding your issue, you need to be sure that proxy is only one source of requests to kucoin API. If not, maybe your server has the same IP that another doing a lot of requests?

from exchange-proxy.

Hi Mike,

Thanks for replying so fast.

Regarding the 429 this does not happen anymore since I installed you proxy :-)

Regarding the second paragraph, I don't know how to check that :-/ rather unexperimented with FT and such type of verification.

What I can say is that, I have, 5 FreqTrade bots running ... 2 live bots and 3 dry bots

The thing that could (maybe imho) make thing go wrong is maybe that these 5 strats are using different timeframe value :-/

Bot1 : is using timeframe = 1m
Bot2 : is using timeframe = 5m
Bot3 : is using timeframe = 15m
Bot4 : is using timeframe = 5m
Bot5 : is using timeframe = 15m

I only have one VPS server with FreqTrade installed on it and those 5 strats.

Is there something I could verify more deeply in order fo you to help me solve this issue ?

NB: Fyi, BUYS adn SELLS are happening normaly in Live and in Dry mode.

Thanks for your support.

from exchange-proxy.

Q: The thing that could (maybe imho) make thing go wrong is maybe that these 5 strats are using different timeframe value :-/
A: It's fine. Proxy optimizing these requests, so your machine does not overflow kucoin API with sending unnecessary requests.

What is the VPS provider? Could you change the IP of your server over the admin interface?

If you are sure that there are no request sources to kucoin API I think you have to ask for their support.

from exchange-proxy.

OK ...

The VPS Provider is : Oracle in Japan (I have a paid subscription but using it in the limits of the Free Tier.)

Regarding the other eventual request ... the only thing I do is accessing the FreqUI interfaces via remote SSH connection ... I don't think this is a problem right ?

from exchange-proxy.

Regarding the other eventual request ... the only thing I do is accessing the FreqUI interfaces via remote SSH connection ... I don't think this is a problem right ?

You are right, it's not a problem

from exchange-proxy.