Skip to main content

Getting Help

Before diving into troubleshooting, here are the best ways to get help:

Discord Community

Join the community for real-time help and discussions

GitHub Issues

Report bugs and request features

Quick Diagnostics

Run these commands to quickly diagnose common issues:

Installation Issues

Symptom: Shell can’t find the openportal commandSolutions:
  1. Verify installation:
  2. Reinstall globally:
  3. Check Bun global bin path:
    If not present, add to your shell profile:
  4. Use bunx instead:
Symptom: Portal can’t find OpenCode installationSolution: Install OpenCode:
Symptom: EACCES or permission denied errors during installSolutions:
  1. Don’t use sudo with Bun:
  2. Fix Bun permissions:
  3. Reinstall Bun:
Symptom: Errors when running with Node.js instead of BunSolution:
OpenPortal works best with Bun. Node.js may have rough edges.
Install and use Bun:
If you must use Node.js:

Startup Issues

Symptom: Error message about port 3000 or 4000 being busySolutions:
  1. Let Portal auto-find ports:
  2. Specify different ports:
  3. Find what’s using the port:
  4. Stop existing Portal instances:
Symptom: Web UI loads but can’t connect to OpenCode serverDebug steps:
  1. Check if OpenCode port is accessible:
  2. Try starting OpenCode manually:
    Look for error messages in the output.
  3. Check OpenCode logs:
  4. Verify working directory exists:
  5. Check disk space:
Symptom: Browser shows empty white page or loading foreverSolutions:
  1. Hard refresh the page:
    • Chrome/Firefox: Ctrl+Shift+R (Cmd+Shift+R on Mac)
    • Safari: Cmd+Option+R
  2. Clear browser cache:
    • Chrome: Settings > Privacy > Clear browsing data
    • Firefox: Preferences > Privacy > Clear Data
    • Safari: Preferences > Privacy > Manage Website Data
  3. Check browser console for errors:
    • Open DevTools: F12 or Ctrl+Shift+I
    • Look for errors in Console tab
  4. Try different browser:
  5. Check if server is actually responding:
Symptom: Portal works on localhost but not from other devicesSolutions:
  1. Bind to all interfaces:
  2. Check firewall rules:
  3. Verify Portal is listening on 0.0.0.0:
  4. Test connectivity:

Connection Issues

Symptom: “Connection lost” or “Reconnecting…” messagesSolutions:
  1. Check if OpenCode server is running:
  2. Restart Portal:
  3. Check server logs:
  4. Verify network connectivity:
  5. Check for resource issues:
Symptom: Portal feels sluggish, AI responses take very longDebug steps:
  1. Check system resources:
  2. Check disk I/O:
  3. Verify network latency (for remote access):
  4. Check OpenCode model settings:
    • Larger models (GPT-4, Claude Opus) are slower
    • Try a faster model for testing
  5. Restart with clean state:
Symptom: Real-time updates not working, need to refresh manuallySolutions:
  1. Check for reverse proxy issues: If using Nginx, ensure WebSocket headers are configured:
  2. Check firewall doesn’t block WebSockets:
  3. Browser extensions interfering:
    • Try in incognito/private mode
    • Disable ad blockers and privacy extensions

Session Issues

Symptom: Create session button doesn’t work or errors outSolutions:
  1. Check OpenCode server is accessible:
  2. Verify permissions on OpenCode config directory:
  3. Check disk space:
  4. Try creating session via OpenCode CLI:
Symptom: Created sessions but they don’t appear in the listDebug:
  1. Check OpenCode sessions directory:
  2. Verify API is returning sessions:
  3. Refresh the browser:
    • F5 or Ctrl+R
  4. Check browser console for errors:
    • F12 > Console tab
Symptom: Delete button doesn’t work or session reappearsSolutions:
  1. Check file permissions:
  2. Delete manually:
  3. Verify not open in another instance:
    • Close all OpenCode instances
    • Try deleting again
Symptom: Open a session but messages don’t appearSolutions:
  1. Check session file exists:
  2. Verify JSON is valid:
  3. Check browser console:
    • F12 > Console > Look for parsing errors
  4. Try opening in official OpenCode CLI:

Mobile-Specific Issues

Symptom: Portal works on server but not accessible from phoneSolutions:
  1. Verify Tailscale is connected on both devices:
  2. Verify Portal bound to 0.0.0.0:
  3. Test connectivity:
  4. Try IP address instead of hostname:
See Tailscale Setup Guide for detailed troubleshooting.
Symptom: UI elements too small or not clickable on mobileSolutions:
  1. Hard refresh the page:
    • Safari: Pull down to refresh
    • Chrome: Menu > Reload
  2. Clear mobile browser cache:
    • Safari: Settings > Safari > Clear History and Website Data
    • Chrome: Settings > Privacy > Clear browsing data
  3. Try different mobile browser:
    • iOS: Safari, Chrome, Firefox
    • Android: Chrome, Firefox, Samsung Internet
  4. Check if Desktop mode is enabled:
    • Disable “Request Desktop Site”
  5. Report UI issue with screenshots:
Symptom: Connection drops when switching apps or locking screeniOS Solutions:
  • Settings > Tailscale > Allow unlimited background activity
  • Disable Low Power Mode while using Portal
  • Keep Portal tab active (don’t close)
Android Solutions:
  • Settings > Apps > Tailscale > Battery > Unrestricted
  • Settings > Apps > Browser > Battery > Unrestricted
  • Enable “Always-on VPN” in Tailscale settings

Performance Issues

Symptom: Portal or OpenCode consuming excessive RAMSolutions:
  1. Check actual memory usage:
  2. Limit resources with systemd:
  3. Delete old sessions:
  4. Restart Portal regularly:
  5. Use lighter AI model:
    • Switch from Claude Opus to Sonnet
    • Use GPT-3.5 instead of GPT-4
Symptom: Server CPU constantly high even when idleDebug:
  1. Identify CPU-hungry process:
  2. Check for infinite loops in code:
    • Review recent changes
    • Check OpenCode logs for errors
  3. Verify no stuck sessions:
  4. Check for disk I/O bottleneck:
Symptom: AI takes very long to respond or times outFactors:
  1. Model speed varies:
    • GPT-4, Claude Opus: Slowest but best quality
    • GPT-4 Turbo, Claude Sonnet: Balanced
    • GPT-3.5: Fastest but lower quality
  2. API rate limits:
    • Check your OpenAI/Anthropic account for rate limits
    • Upgrade API tier if needed
  3. Network latency:
  4. Large context:
    • Large codebases take longer to process
    • Mention fewer files to reduce context
  5. Check OpenCode logs:

File Operations

Symptom: File autocomplete doesn’t work or files not foundSolutions:
  1. Verify you’re in correct directory:
  2. Check file permissions:
  3. Relative vs absolute paths:
    • Use relative paths: @src/index.ts
    • Not absolute: ~/project/src/index.ts
  4. File indexing:
    • OpenCode indexes files on start
    • Restart if new files not appearing
Symptom: Portal hangs when mentioning large filesWorkarounds:
  1. Check file size:
  2. Avoid mentioning very large files:
    • Binary files
    • Generated files (build output, node_modules)
    • Database dumps
  3. Use .gitignore patterns:
    • OpenCode respects .gitignore
    • Add large files to .gitignore
  4. Mention specific sections: Instead of mentioning entire file, describe the section: “The login function in @auth.ts around line 50”

Data and Configuration

To start fresh:
Portal stores data in:
  • Registry: ~/.config/openportal/registry.json
  • Logs: System logs (check with journalctl if using systemd)
OpenCode stores data in:
  • Sessions: ~/.config/opencode/sessions/
  • Config: ~/.config/opencode/config.json
  • Logs: ~/.config/opencode/logs/
Backup important data:
Migration steps:
  1. On old server, backup sessions:
  2. On new server, install everything:
  3. Restore sessions:
  4. Set up Tailscale: See Tailscale Setup Guide
  5. Start Portal:

Error Messages

Meaning: The port is already occupied by another processFix:
Meaning: Can’t connect to OpenCode serverFix:
Meaning: Disk is fullFix:
Meaning: Network request took too longFix:

Still Having Issues?

Ask on Discord

Get help from the community in real-time

Open GitHub Issue

Report bugs or request features
When asking for help, please include:
  1. Operating system and version
  2. Bun version: bun --version
  3. OpenCode version: opencode --version
  4. Portal version: openportal --version (if available)
  5. Full error message or logs
  6. Steps to reproduce the issue
  7. What you’ve already tried
Gather diagnostic information:

Next Steps