user430: I'm setting up my environment to run the example from lecture #1 (Week01 auction)
All compilations went well but when I try the evaluate in the simulator I always receive:
interpreter Errors
ConnectionError (HttpExceptionRequest Request { host = "localhost" port = 8080 secure = False requestHeaders = [("Accept","application/json;charset=utf-8,application/json"),("Content-Type","application/json;charset=utf-8")] path = "/runghc" queryString = "" method = "POST" proxy = Nothing rawBody = False redirectCount = 10 responseTimeout = ResponseTimeoutDefault requestVersion = HTTP/1.1 } ResponseTimeout)
Please try again or contact support for assistance.

The plutus-playground-server log has the smartcontract and the datum so I think that the call for evaluation was correctly sent but somehow it doesn't come back to the client. In my opinion it's more an issue related to the npm but I don't know how to debug it.
I'm using Ubuntu, all the work done through nix-shell. Plutus tag: 3746610e53654a1167aeb4c6294c6096d16b0502
UPDATE
Further analysis brings me to the conclusion that my system is too slow for the client-server interaction. I saw that the issue is related only to the Auction contract (that's heavier than the demo ones) and watching the trace of the HTTP calls i notice that the /runghc POST takes 34 seconds to give back an answer.
Is there any way i can configure the playground server to consider a timeout higher than 30 secs?

user2009: You can try configuring the timeout in cardano/plutus/plutus-playground-client/webpack.config.js
devServer: {
    contentBase: path.join(__dirname, "dist"),
    compress: true,
    port: 8009,
    https: true,
    proxy: {
        "/api": {
            target: 'http://localhost:8080'
            timeout: 1000 * 60 * 10
        }
    } },

There also appears to be a proxyTimeout setting that you can try.
I can't reproduce the error on my end so I'm not sure if this will work, but it seems to make sense that the webpack server is timing out.
Here is a general question posted about webpack dev server timeouts that suggest trying the configurations I mentioned above.
https://stackoverflow.com/questions/47217090/how-can-i-let-webpack-dev-server-have-incoming-request-timeout-with-custom-value

430: <p>I'm setting up my environment to run the example from lecture #1 (Week01 auction)</p>
<p>All compilations went well but when I try the evaluate in the simulator I always receive:</p>
<pre><code>interpreter Errors
ConnectionError (HttpExceptionRequest Request { host = &quot;localhost&quot; port = 8080 secure = False requestHeaders = [(&quot;Accept&quot;,&quot;application/json;charset=utf-8,application/json&quot;),(&quot;Content-Type&quot;,&quot;application/json;charset=utf-8&quot;)] path = &quot;/runghc&quot; queryString = &quot;&quot; method = &quot;POST&quot; proxy = Nothing rawBody = False redirectCount = 10 responseTimeout = ResponseTimeoutDefault requestVersion = HTTP/1.1 } ResponseTimeout)
Please try again or contact support for assistance.
</code></pre>
<p>The plutus-playground-server log has the smartcontract and the datum so I think that the call for evaluation was correctly sent but somehow it doesn't come back to the client. In my opinion it's more an issue related to the npm but I don't know how to debug it.</p>
<p>I'm using Ubuntu, all the work done through nix-shell. Plutus tag: <code>3746610e53654a1167aeb4c6294c6096d16b0502</code></p>
<p><strong>UPDATE</strong></p>
<p>Further analysis brings me to the conclusion that my system is too slow for the client-server interaction. I saw that the issue is related only to the Auction contract (that's heavier than the demo ones) and watching the trace of the HTTP calls i notice that the /runghc POST takes 34 seconds to give back an answer.</p>
<p>Is there any way i can configure the playground server to consider a timeout higher than 30 secs?</p>
 2009: <p>You can try configuring the timeout in <code>cardano/plutus/plutus-playground-client/webpack.config.js</code></p>
<pre><code>devServer: {
    contentBase: path.join(__dirname, &quot;dist&quot;),
    compress: true,
    port: 8009,
    https: true,
    proxy: {
        &quot;/api&quot;: {
            target: 'http://localhost:8080'
            timeout: 1000 * 60 * 10
        }
    } },
</code></pre>
<p>There also appears to be a <code>proxyTimeout</code> setting that you can try.</p>
<p>I can't reproduce the error on my end so I'm not sure if this will work, but it seems to make sense that the webpack server is timing out.</p>
<p>Here is a general question posted about webpack dev server timeouts that suggest trying the configurations I mentioned above.</p>
<p><a href="https://stackoverflow.com/questions/47217090/how-can-i-let-webpack-dev-server-have-incoming-request-timeout-with-custom-value">https://stackoverflow.com/questions/47217090/how-can-i-let-webpack-dev-server-have-incoming-request-timeout-with-custom-value</a></p>
