Private app stuck loading — HTTP 500 on /~/+/, RUNNING status and empty logs

Community Cloud
1

Hi,

Our private app is stuck on the loading spinner.

What we observed:

  • GET /~/+/ returns HTTP 500.
  • Its response redirects to https://share.streamlit.io/error.
  • The app status shows RUNNING, but Cloud logs remain empty.
  • The issue was observed around 08:54 UTC on October 5, 2026.

We have tried:

  • Rebooting the app.
  • Signing out and back into Streamlit Community Cloud.
  • Opening it in Chrome and Safari.
  • Opening it directly from My Apps.
  • Reverting the latest favicon change. The repository now exactly matches the version before that change.

The issue persists. Could the Streamlit team check the deployment health and routing for this app?

Snowflake Support referred us here under case #01484065.
Thank you.

2

Hey there, thanks for the detailed report and for sharing all your troubleshooting steps—welcome to the Streamlit community! :unicorn: You’re not alone: a private app stuck on the loading spinner with HTTP 500s and empty Cloud logs is a known symptom of a backend or routing issue on Streamlit Community Cloud, especially when the app status shows RUNNING but nothing loads, and rebooting or reverting code doesn’t help. This often points to a platform-level problem rather than anything in your repo or config, and several users have reported similar issues recently, sometimes linked to temporary outages or infrastructure changes on Streamlit’s side.

When Cloud logs are empty and you see HTTP 500s or redirects to /error, it’s usually not something you can fix from your end—especially since you’ve already tried rebooting, reverting changes, and using different browsers. The best next step is to monitor the Streamlit status page and relevant forum threads for outage updates, as these incidents are typically resolved by the engineering team without user intervention. If you haven’t already, you can also try deleting and redeploying the app (this won’t affect your repo or analytics, but always keep a backup). For more info, see the official docs on app management and resource limits, and check out similar community reports for context. Community members, feel free to jump in if you’ve seen a recent workaround!

Sources: