Tobia De Koninck

Hi Are you running any reverse proxies or loadbalancer in front of ShinyProxy? If so, these are causing the 504 timeout errors. You should update the configuration of the proxy...

I'm unable to reproduce this issue. It seems like the `docker-proxy` command keeps running, even when the container was already stopped. Could you share the following information? - operating system...

Thank you for the details, the issue with ZFS sounds interesting, I could try to use a ZFS host. At least it seems your server has enough resources, so I...

Hi @spinanicky I was not able to reproduce this consistently, but I have seen it happening a few times randomly as well. As mentioned above it seems the `docker-proxy` process...

Can you post your `application.yml` file and the configuration of nginx? How long does it takes to load the page before you get the timeout?

That configuration should work and cause no timeouts. Are you sure it's configured at the correct location? (i.e. in the correct server block) If so, I suspect you have another...

Hi @spinanicky that is unfortunate, I'll continue having a look. When you notice the issue, do you perhaps have (some) containers that failed to start? It seems I recently observed...

Hi I found a potential issue and implemented a fix. Can you try with the docker image `openanalytics/shinyproxy-snapshot:3.1.1-SNAPSHOT-20240606.143229 ` or this jar: https://nexus.openanalytics.eu/repository/snapshots/eu/openanalytics/shinyproxy/3.1.1-SNAPSHOT/shinyproxy-3.1.1-20240606.143229-2-exec.jar

Hi, ShinyProxy 3.0.0 changed the behavior when starting an app. Instead of performing a single HTTP request to start an app, it sends multiple requests and each request is limited...

Okay, thanks for letting us know. We just released ShinyProxy 3.1.1, which includes the fix, so I'm going to close this.