Traiding pairs not showing up

[taji]

trading pairs are blank anyone no why

[Aitor]

Hi, can you show me a pic of what gunthy-win.exe is showing please?

[taji]

2020/04/18 11:31:14: Kicking binance, receiving new tickers...
2020/04/18 11:31:25: Kicking bybit, receiving new tickers...
2020/04/18 11:31:47: Kicking binance, receiving new tickers...
2020/04/18 11:31:47: Kicking bitmex, receiving new tickers...
2020/04/18 11:31:58: Kicking bybit, receiving new tickers...
2020/04/18 11:32:19: Kicking binance, receiving new tickers...
2020/04/18 11:32:20: Kicking bitmex, receiving new tickers...
2020/04/18 11:32:31: Kicking bybit, receiving new tickers...
2020/04/18 11:32:51: Kicking binance, receiving new tickers...
2020/04/18 11:32:54: Kicking bitmex, receiving new tickers...
2020/04/18 11:33:05: Kicking bybit, receiving new tickers...
2020/04/18 11:33:23: Kicking binance, receiving new tickers...
2020/04/18 11:33:27: Kicking bitmex, receiving new tickers...
2020/04/18 11:33:38: Kicking bybit, receiving new tickers...
2020/04/18 11:33:55: Kicking binance, receiving new tickers...
2020/04/18 11:34:01: Kicking bitmex, receiving new tickers...

its doing this ..

thank u for your time

[taji]

[Aitor]

What platform are you running the bot on?
I saw a customer who was running the bot fine with v18.8.8 on Windows and he started getting this on ARM.

[taji]

Windows

[Aitor]

You are using VPN, it can make the communication with your browser to be incomplete. Please try to close the bot, disconnect VPN and try again. On the other hand, what version are you running?

[taji]

i was running 18 but i switched back to 16 no problems

[Aitor]

Glad to hear you fixed it 

[flensje]

Glad to hear you fixed it 

No offense but...This isn't really fixed, it's been worked around. The actual problem with v18 isn't solved.
I also receive this error using Binance. It runs one cycle of defined pairs and then starts giving back "Kicking Binance, receiving new tickers"
Debug switched on in the web interface does not give back more useful information on this.

Could this issue be addressed or somehow explained why this is happening?

Thanks!
flensje

[Aitor]

Glad to hear you fixed it 

No offense but...This isn't really fixed, it's been worked around. The actual problem with v18 isn't solved.
I also receive this error using Binance. It runs one cycle of defined pairs and then starts giving back "Kicking Binance, receiving new tickers"
Debug switched on in the web interface does not give back more useful information on this.

Could this issue be addressed or somehow explained why this is happening?

Thanks!
flensje

Hi, note that exchanges sometimes make some upgrades / changes / maintenance that makes the bot to get some undesired errors. Despite v18.8.8 is the latest stable version, v19 beta fixes some of these issues and in some cases the update is necessary. In this case, the upgrade to v19 will fix the issue. For those who use ARM, considering that there isn't still v19 for ARM, I have seen that in some cases, the installation of 18.3.9 + remove JSON directory has fixed some issues like this one. Obv the best solution is to update to latest v19 version.