Run any Skill in Manus with one click

streamlit-private-troubleshoot

Stars0

Forks0

UpdatedJune 4, 2026 at 20:21

Diagnose a failed streamlit-private deployment or broken private access — missing provider secrets, proxy/WebSocket issues, auth/membership problems, or a misconfigured manifest. Use when the user says "my deploy failed", "the app won't load", "sign-in is broken", or "the page is blank / keeps reconnecting".

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

DecisionNerd

DecisionNerd/streamlit-private

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	streamlit-private-troubleshoot
description	Diagnose a failed streamlit-private deployment or broken private access — missing provider secrets, proxy/WebSocket issues, auth/membership problems, or a misconfigured manifest. Use when the user says "my deploy failed", "the app won't load", "sign-in is broken", or "the page is blank / keeps reconnecting".

streamlit-private: troubleshoot

Diagnose problems with a streamlit-private deployment by reading the manifest, logs, and host status, then propose fixes. This skill is read-only by default — it gathers evidence and suggests actions; it does not apply changes silently.

When to use

A deploy failed, the app won't load, sign-in is broken, or the page is blank / keeps reconnecting (a classic WebSocket-proxy symptom).
The user reports any private-access or deployment problem.

Hard rules

Read-only by default. Inspect configuration, logs, and status. Propose fixes and explain them; do not apply changes, redeploy, or reconfigure without the user's go-ahead.
Never edit the user's application files while diagnosing.
Never print secret values. Check whether a secret is set, not what it is.
Do not reimplement the CLI. Use streamlit-private and the host's own status/logs.

Steps

Read streamlit-private.yaml to confirm the configured auth and hosting providers.
Check that required provider secrets are set (presence only — see .env.example for the list); a missing auth/hosting key is the most common failure.
Inspect deployment logs and host status for the gateway and the Streamlit service.
Match symptoms to likely causes:
- Blank page / "connection failed" / constant reconnect → WebSocket upgrade or proxy path issue at the gateway (_stcore / _static / _media).
- Stuck at sign-in or "access denied" → auth provider misconfiguration, wrong keys, or the user isn't an org member (consider streamlit-private-invite / streamlit-private-access-requests).
- Deploy never completes → hosting provider build/runtime error in the logs.
- CLI says "already configured" / "not a Streamlit app" → wrong directory or state; route to streamlit-private-init or streamlit-private-configure.
Report findings and a proposed fix, and ask the user before acting (e.g. before re-running deploy via the streamlit-private-deploy skill or configure).

Notes

The most frequent root causes are missing/incorrect provider secrets and the WebSocket proxy path — check those first.

More from this repository

same repository

streamlit-private-deploy

DecisionNerd/streamlit-private

Deploy a streamlit-private project to a managed host (Railway first; Render/Fly.io later) and return the private, authenticated URL. Use when the user wants to "deploy my Streamlit app", "ship it", "put it online privately", or "deploy to Railway".

2026-06-050

streamlit-private-access-requests

DecisionNerd/streamlit-private

List and act on pending access requests for a privately deployed Streamlit app — approve (add the user to the organization) or reject them via streamlit-private. Use when the user (an admin) wants to "approve access requests", "see who's requested access", or "let someone in".

2026-06-040

streamlit-private-configure

DecisionNerd/streamlit-private

Reconfigure an existing streamlit-private project — switch the auth provider (e.g. Clerk → WorkOS) or hosting provider (e.g. Railway → Render), or regenerate deployment assets, while preserving the user's application code. Use when the user wants to "change auth provider", "switch hosting", or "regenerate my streamlit-private config".

2026-06-040

streamlit-private-init

DecisionNerd/streamlit-private

Initialize a Streamlit app for private deployment with streamlit-private — scaffold a new app or wrap an existing Streamlit repo, adding a gateway, deployment assets, and a manifest without touching application code. Use when the user wants to "make my Streamlit app private", "set up streamlit-private", or "add auth to my Streamlit app".

2026-06-040

streamlit-private-invite

DecisionNerd/streamlit-private

Invite a user to a privately deployed Streamlit app's organization via streamlit-private, so they become a member and gain access. Use when the user (an admin) wants to "invite someone", "add a user", or "give my colleague access" to the app.

2026-06-040

name	streamlit-private-troubleshoot
description	Diagnose a failed streamlit-private deployment or broken private access — missing provider secrets, proxy/WebSocket issues, auth/membership problems, or a misconfigured manifest. Use when the user says "my deploy failed", "the app won't load", "sign-in is broken", or "the page is blank / keeps reconnecting".

streamlit-private: troubleshoot

When to use

A deploy failed, the app won't load, sign-in is broken, or the page is blank / keeps reconnecting (a classic WebSocket-proxy symptom).
The user reports any private-access or deployment problem.

Hard rules

Read-only by default. Inspect configuration, logs, and status. Propose fixes and explain them; do not apply changes, redeploy, or reconfigure without the user's go-ahead.
Never edit the user's application files while diagnosing.
Never print secret values. Check whether a secret is set, not what it is.
Do not reimplement the CLI. Use streamlit-private and the host's own status/logs.

Steps

Read streamlit-private.yaml to confirm the configured auth and hosting providers.
Check that required provider secrets are set (presence only — see .env.example for the list); a missing auth/hosting key is the most common failure.
Inspect deployment logs and host status for the gateway and the Streamlit service.
Match symptoms to likely causes:
- Blank page / "connection failed" / constant reconnect → WebSocket upgrade or proxy path issue at the gateway (_stcore / _static / _media).
- Stuck at sign-in or "access denied" → auth provider misconfiguration, wrong keys, or the user isn't an org member (consider streamlit-private-invite / streamlit-private-access-requests).
- Deploy never completes → hosting provider build/runtime error in the logs.
- CLI says "already configured" / "not a Streamlit app" → wrong directory or state; route to streamlit-private-init or streamlit-private-configure.
Report findings and a proposed fix, and ask the user before acting (e.g. before re-running deploy via the streamlit-private-deploy skill or configure).

Notes

The most frequent root causes are missing/incorrect provider secrets and the WebSocket proxy path — check those first.