Error when running streamlit app in a netlify website.

My github settings are all good and streamlit app settings appear to be good but when I try to run the app from the website i get the following error:

Here is a screenshot of the app settings.

Hey there, thanks for sharing your question and screenshots! :blush: The error “You do not have access to this app or it does not exist” on Streamlit Community Cloud, even when your GitHub and app settings look correct, is usually caused by a mismatch or change in your app’s GitHub coordinates (repo name, branch, or entrypoint file), or by account linking issues. If you’ve recently renamed your repo, changed branches, or moved the entrypoint file, Streamlit may lose track of your app’s source, resulting in this error—even if the app’s URL and settings appear fine. This can also happen if your GitHub account isn’t properly linked as the source control for your Streamlit account, or if you’re signed in with a different email than the one associated with your GitHub account.

To resolve this, follow these steps:

  1. Check GitHub Coordinates: If you changed your repo name, branch, or entrypoint file, you must delete the app in Streamlit Community Cloud and redeploy it with the new coordinates. See Rename or change your app’s GitHub coordinates.
  2. Verify Account Linking: Make sure you’re signed in to Streamlit Community Cloud with the same GitHub account used to deploy the app. If you have multiple accounts, sign out of all, then sign in first with your email (or Google), then with GitHub. See Update your email and Manage your GitHub connection.
  3. Check App Visibility: If your repo is private, ensure Streamlit has access to private repos in your GitHub settings. If you moved the repo between organizations or accounts, update permissions accordingly.
  4. Workspace Matching: Make sure you’re in the correct workspace that matches the repo owner. See Explore your workspace.

If you’ve done all this and still see the error, try deleting and redeploying the app, or change the subdomain temporarily and then switch it back. For more details and community troubleshooting, see this forum thread and this one. If you’re still stuck, please share a minimum reproducible example or your repo link so the community can help debug. Community members, feel free to jump in with your insights!

Sources: