tag:support.appharbor.com,2010-11-23:/discussions/problems/94288-aspnet-core-slowAppHarbor: Discussion 2018-01-13T05:40:30Ztag:support.appharbor.com,2010-11-23:Comment/444896172018-01-13T05:40:29Z2018-01-13T05:40:29ZASP.NET Core 502 - Web server received an invalid response while acting as a gateway or proxy server.<div><p>Hi Bob,</p>
<p>Since the issue appears to occur at startup you may want to minimize the time it takes to warm up. You likely don't experience this issue when you redeploy your application as AppHarbor will warm up the new worker before routing data to it (for up to at least 2 minutes on the free plan). However, applications on the Canoe plan will time out after 20 minutes of inactivity, so if your app isn't accessed for a while it'll cause the app to respond slower when it's restarted.</p>
<p>You can likely avoid this by upgrading to the Catamaran plan. Workers on that (and the Yacht) plan will only idle out after 36 hours of inactivity. Apps on the paid plans also have 5 minutes to warm up before AppHarbor starts routing traffic to it, and you get an extra worker unit you can use to scale the app vertically (and get twice as much CPU resources which is often the bottleneck during startup).</p>
<p>I hope this helps, but please don't hesitate to reach out if there's anything else I can help with!</p>
<p>Best,<br>
Rune</p></div>rune