Long Gekko backtest causing econnect timeout solution

When I run backtests over 3-5 months that use multiple talib (yuck!) indicators I often get an econnect error. This was a major pain to fix, but seems to be to do with the socket timeout. Below is the fix:

Edit server.js and add the line in bold below the websocket server reference:

const wss = new WebSocketServer({ server: server });
wss._server.timeout = 50000000;