replit-common-errors
A troubleshooting guide for resolving frequent Replit runtime, configuration, and deployment errors.
Install
mkdir -p .claude/skills/replit-common-errors && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/6608" && unzip -o skill.zip -d .claude/skills/replit-common-errors && rm skill.zipInstalls to .claude/skills/replit-common-errors
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Diagnose and fix the top Replit errors: container sleep, port binding,Key capabilities
- →Diagnose container sleep issues
- →Resolve port binding conflicts
- →Fix Nix package configuration
- →Debug database connection errors
How it works
Provides a systematic troubleshooting guide for common Replit environment errors, focusing on container lifecycle, Nix dependencies, and environment variables.
Inputs & outputs
When to use replit-common-errors
- →Fix port binding address errors
- →Address container sleep issues
- →Debug failed deployments
- →Troubleshoot networking issues in repls
About this skill
Replit Common Errors
Overview
Quick reference for the 10 most common Replit errors with real solutions. Covers container lifecycle, Nix configuration, database, deployment, and networking issues.
Prerequisites
- Replit Workspace access
- Shell tab for diagnostics
- Console tab for error logs
Error Reference
1. Container Sleeping / App Goes Offline
Error: Your Repl is sleeping. Run it to wake up.
Cause: Free/Hacker plan Repls sleep after ~5 minutes of inactivity. Solution:
- Use Replit Deployments (Autoscale or Reserved VM) for always-on
- Or set up external keep-alive pinging (UptimeRobot, cron-job.org)
- Check: Settings > Always On (deprecated in favor of Deployments)
2. Port Binding / Webview Not Loading
Error: EADDRINUSE: address already in use :::3000
Cause: Previous process still holding the port, or hardcoded port conflicts. Solution:
# Find and kill the process
lsof -i :3000 | grep LISTEN
kill -9 <PID>
# Or use environment variable for port
// Always use PORT env var
const port = parseInt(process.env.PORT || '3000');
app.listen(port, '0.0.0.0'); // Must be 0.0.0.0, not localhost
3. Nix Package Build Failure
Error: error: Package 'python-xyz' not found in channel 'stable-23_05'
Cause: Package name wrong, or Nix channel too old. Solution:
# replit.nix — update channel and fix package names
{ pkgs }: {
deps = [
pkgs.nodejs-20_x # not "nodejs" or "node"
pkgs.python311 # not "python3" or "python"
pkgs.python311Packages.pip # not "pip"
pkgs.zlib # for native modules (Pillow, etc.)
pkgs.openssl # for crypto dependencies
];
}
# .replit — use current stable channel
[nix]
channel = "stable-24_05"
After editing replit.nix, reload the shell (exit and re-enter Shell tab).
4. DATABASE_URL Not Set
Error: Connection refused / ECONNREFUSED / DATABASE_URL is undefined
Cause: PostgreSQL not provisioned, or accessing outside Replit. Solution:
- Open the Database pane in the sidebar
- Click "Create a database" if none exists
DATABASE_URLauto-populates in your environment- For legacy Replit DB: check
REPLIT_DB_URLinstead
5. Replit DB Write Failure (50MB Limit)
Error: Max storage size exceeded
Cause: Key-Value Database has a 50 MiB total limit (keys + values). Solution:
# Check current usage
from replit import db
total_keys = len(list(db.keys()))
print(f"Keys: {total_keys} / 5000")
# Migrate large data to Object Storage or PostgreSQL
from replit.object_storage import Client
storage = Client()
storage.upload_from_text('large-data.json', json.dumps(big_data))
del db['large_key'] # Free up KV space
6. Object Storage Bucket Not Found
Error: BucketNotFoundError: No bucket found
Cause: Object Storage bucket not provisioned for this Repl. Solution:
- Open the Object Storage pane in the sidebar
- Create a new bucket (auto-names based on Repl)
- Then use
new Client()with no arguments — it auto-discovers
7. Auth Headers Empty
req.headers['x-replit-user-id'] === undefined
Cause: Replit Auth only works on deployed apps (.replit.app or custom domain), not in the Workspace Webview during development.
Solution:
// Mock auth in development
function getUser(req: Request) {
const userId = req.headers['x-replit-user-id'] as string;
if (!userId && process.env.NODE_ENV !== 'production') {
return { id: 'dev-user', name: 'Developer', image: '' };
}
if (!userId) return null;
return {
id: userId,
name: req.headers['x-replit-user-name'] as string,
image: req.headers['x-replit-user-profile-image'] as string,
};
}
8. Module Not Found After Nix Change
Error: Cannot find module '@replit/database'
Cause: npm packages need separate install from Nix system packages. Solution:
# Nix = system packages (Python runtime, PostgreSQL, etc.)
# npm/pip = language packages (express, flask, etc.)
# Both are needed:
# In replit.nix: pkgs.nodejs-20_x
# In shell: npm install @replit/database @replit/object-storage
# For Python:
# In replit.nix: pkgs.python311
# In shell: pip install replit flask
9. Deployment Build Timeout
Error: Build exceeded time limit
Cause: Heavy dependencies or slow build step. Solution:
# .replit — optimize build
[deployment]
build = ["sh", "-c", "npm ci --production && npm run build"]
run = ["sh", "-c", "node dist/index.js"]
# Tips:
# - Use npm ci instead of npm install
# - Use --production to skip devDependencies
# - Use TypeScript incremental builds: tsc --incremental
# - Remove unused packages from package.json
10. Secrets Not Available in Deployment
Error: API_KEY is undefined in production
Cause: Secrets added in Workspace may not have synced (legacy behavior). Solution:
- As of 2025, deployment secrets sync automatically with Workspace secrets
- Verify in Deployments > Settings > Environment Variables
- For Account-level secrets: Settings > Secrets (applies to all Repls)
- Restart the deployment after adding secrets
Quick Diagnostics
# Check Replit status
curl -s https://status.replit.com/api/v2/summary.json | jq '.status.description'
# Check built-in env vars
echo "REPL_SLUG=$REPL_SLUG"
echo "REPL_OWNER=$REPL_OWNER"
echo "REPLIT_DB_URL=${REPLIT_DB_URL:+SET}"
echo "DATABASE_URL=${DATABASE_URL:+SET}"
# Check installed packages
npm list --depth=0 2>/dev/null
pip list 2>/dev/null | head -20
Resources
Next Steps
For comprehensive debugging, see replit-debug-bundle.
When not to use it
- →Do not use local development auth headers in production
Prerequisites
Limitations
- →Replit KV has a 50 MiB total limit
- →Replit Auth only works on deployed apps
How it compares
Provides specific Replit-native solutions for common errors rather than generic debugging steps.
Compared to similar skills
replit-common-errors side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| replit-common-errors (this skill) | 1 | 27d | Caution | Beginner |
| memory-mcp | 6 | 29d | Review | Intermediate |
| context-degradation | 3 | 2mo | Review | Advanced |
| langsmith-fetch | 6 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by jeremylongshore
View all by jeremylongshore →You might also like
memory-mcp
d-o-hub
Use and troubleshoot the Memory MCP server for episodic memory retrieval and pattern analysis. Use this skill when working with MCP server tools (query_memory, analyze_patterns, advanced_pattern_analysis), validating the MCP implementation, or debugging MCP server issues.
context-degradation
muratcankoylan
This skill should be used when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, attention patterns, context clash, context confusion, or agent performance degradation. Provides patterns for recognizing and mitigating context failures.
langsmith-fetch
ComposioHQ
Debug LangChain and LangGraph agents by fetching execution traces from LangSmith Studio. Use when debugging agent behavior, investigating errors, analyzing tool calls, checking memory operations, or examining agent performance. Automatically fetches recent traces and analyzes execution patterns. Requires langsmith-fetch CLI installed.
lindy-debug-bundle
jeremylongshore
Comprehensive debugging toolkit for Lindy AI agents. Use when investigating complex issues, collecting diagnostics, or preparing support tickets. Trigger with phrases like "lindy debug", "lindy diagnostics", "lindy support bundle", "investigate lindy issue".
skill-tuning
catlog22
Universal skill diagnosis and optimization tool. Detect and fix skill execution issues including context explosion, long-tail forgetting, data flow disruption, and agent coordination failures. Supports Gemini CLI for deep analysis. Triggers on "skill tuning", "tune skill", "skill diagnosis", "optimize skill", "skill debug".
agent-introspection-debugging
ThanhTrunggDEV
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports.