+- Gekko Forum (https://forum.gekko.wizb.it)
+-- Forum: Gekko (https://forum.gekko.wizb.it/forum-13.html)
+--- Forum: Technical Discussion (https://forum.gekko.wizb.it/forum-23.html)
+--- Thread: Issue: 502 Bad Gateway when Backtesting (/thread-58048.html)
Issue: 502 Bad Gateway when Backtesting - gurkentier - 12-09-2019
Hello,
I am running Gekko v0.6.8 and Gekko UI v0.2.3 and use Nginx as a reverse proxy.
I am encountering an issue when backtesting on bigger time ranges.
I did a backtest on a 11 month date range for USD <-> XRP on binance.
When I choose a range smaller than 1 month, the backtest works just fine.
If I choose a bigger range, the client gets an 502 Bad Gateway from my nginx.
The nginx error log says:
2019/12/09 08:26:40 [error] 3116#3116: *325 connect() failed (111: Connection refused) while connecting to upstream, client: 46.189.28.77, server: _, request: "GET /app.5e99ecf7.js.map HTTP/1.1", upstream: "http://[::1]:3001/app.5e99ecf7.js.map", host: "censored.com"
2019/12/09 08:26:44 [error] 3116#3116: *236 upstream prematurely closed connection while reading response header from upstream, client: 46.189.28.77, server: _, request: "POST /api/backtest HTTP/1.1", upstream: "http://127.0.0.1:3001/api/backtest", host: "censored.com", referrer: "http://censored.com/"
Using the RSI_BB_ADX_PEAK strategy with following params:
# SMA Trends
SMA_long = 220
SMA_short = 21
# BULL
BULL_RSI = 29
BULL_RSI_high = 76
BULL_RSI_low = 31
# BEAR
BEAR_RSI = 27
BEAR_RSI_high = 55
BEAR_RSI_low = 24
# MODIFY RSI (depending on ADX)
BULL_MOD_high = 7
BULL_MOD_low = -10
BEAR_MOD_high = 21
BEAR_MOD_low = -7
# ADX
ADX = 17
ADX_high = 75
ADX_low = 26
# Stop Loss
Stop_Loss_Percent = 15
With candle size of 5 minutes and a warmup of 220.
Is there anybody having the same issues and / or knowing a solution for it?
Thank you in advance