Error installing requirements — bullseye-security InRelease expired (happening on brand new apps too)

Deployment
1

I’m getting the same “Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired” error described in other recent threads here. I saw it’s supposed to be fixed for newly created apps, but I deleted my app and created a completely new one today and got the exact same error:

E: Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired (invalid since 18h 20min 44s). Updates for this repository will not be applied.
[15:33:50] ❗️ installer returned a non-zero exit code
[15:33:50] ❗️ Error during processing dependencies! Please fix the error and push an update, or try restarting the app.

App URL: garmin-hlgaxyqwehyrgqutgrhwbj.streamlit.app
Repository: patriciocasas3010-svg/garmin
Branch: claude/garmin-watch-connection-onodog

Could you check if the fix has fully rolled out? Thanks!

2

Hey there, thanks for reaching out and for sharing the details (and welcome if this is your first post! :balloon:). The “Release file for http://deb.debian.org/debian-security/dists/bullseye-security/InRelease is expired” error is a known issue that’s affected many Streamlit Community Cloud users recently. Even after deleting and recreating apps, some users have continued to see this error due to the upstream Debian repository’s expired release file, which is outside of Streamlit’s direct control.

Based on recent forum threads, the Streamlit team has deployed fixes for similar issues, but propagation can take time and may not be instant for all users or regions. The best current advice is to try deleting and redeploying your app again, as this has resolved the issue for some users once the fix was fully live. If the error persists, it’s likely the fix hasn’t fully rolled out to all backend environments yet. Keep an eye on the Streamlit Community Cloud status page and the official forums for updates. If you’re still stuck, please share your repo and a minimal reproducible example so the community can help debug further!

Sources:

3

Hey @patriciocasas3010,

Thanks so much for flagging. This is an issue the team is aware of and the fix is currently in the works! :rocket:

4

Hey @patriciocasas3010 , thanks for reporting the issue to us! We have rolled out a new version to prod which should fix the issue! Please let us know if something is still not working and sorry for the inconvenience :slight_smile: