In the last two days, major exchanges have been hit by walls, and the issue of brokers has become more prominent. But SetProxy doesn't seem to work. The phenomenon: (1) The browser www.okex.com cannot be accessed directly, the instructions are restricted, the proxy address is set to stream access, but exchange.SetProxy still suggests after setting this proxy address: GetDepth: Gethttps://www.okex.com/api/v1/depth.do?symbol=btg_usdt: dial tcp 31.13.65.18:443The semaphore timeout period has expired. (2) exchange. SetProxy set a messy address so that access to Binance can still be accessed normally.
It looks like SetProxy isn't working.
Inventors quantify - small dreamsI've tested it, okay, I wrote a proxy policy https://www.botvs.com/bbs-topic/1559 and deployed a good SS5 service on my proxy server. - (SS5 deployments can be found at https://www.cnblogs.com/soar1688/p/7183722.html) - According to the API documentation, the configuration instructions for the SetProxy function (https://www.botvs.com/api#SetProxy) allow me to access a number of exchanges.
Inventors quantify - small dreamsWait a minute. Let me test it out. I'll reply later.
Inventors quantify - small dreamsSo the best way to deploy a host is to use an overseas server.
The bride too.SetProxy does solve the problem of overlapping and logging, but it will at least double the time spent by the host to access the exchange.