Streamlit deployment fails with GitHub Permission denied (publickey) 3.

Hello,

I’m having trouble deploying my Streamlit application.

Public app URL: https://spaccatura-passaggi.streamlit.app/

GitHub repository: GitHub - frankvairo7-stack/Spaccatura-passaggi: App per gestire i passaggi in auto e dividere i chilometri tra amici. · GitHub

Branch: main

Main file: app.py

Repository visibility: Public

Python version: 3.14

Error message:

Updating the app files has failed:
git pull: exit status 128:
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

Error during processing dependencies!

I have already tried:

  • Confirming that the GitHub repository is public.

  • Revoking and reauthorizing the Streamlit OAuth application.

  • Checking that there are no Deploy Keys in the repository.

  • Creating a completely new deployment.

The same error persists, and the new deployment does not appear in my Streamlit dashboard.

Could you help me identify and fix this issue?

Thank you!

Thanks for the detailed diagnostics. Since the failure is git pull with Permission denied (publickey), it points to Community Cloud’s GitHub access—not your Streamlit code or Python version. The available docs don’t describe a specific fix for this exact SSH error, so I can’t confirm the root cause from the message alone.

  1. Confirm the GitHub account connected to Community Cloud has admin access to the repository; admin access is required to deploy apps. Connect your GitHub account
  2. Check that the app’s repository, branch, and entrypoint coordinates still match GitHub. Community Cloud identifies apps using those coordinates. Manage your GitHub connection
  3. Since you’ve already reauthorized and redeployed, and the error persists, the provided documentation doesn’t establish another user-side fix. Share the deployment logs and repository details with Streamlit support; a minimal reproducible app can help the community investigate. Note that Python 3.14 isn’t identified in the available sources as the cause of this GitHub authentication failure.

Sources: