Troubleshooting

Symptoms

• •Browser shows "Your connection is not private" error
• •Applications fail to connect with certificate errors
• •ERR_CERT_AUTHORITY_INVALID in Chrome

Possible Causes

• •CA certificate not installed in system trust store
• •Certificate was installed for wrong user
• •Application uses its own certificate store (Firefox, Java)

Solutions

1. 1Open Bleep Settings → Certificates → Click "Install CA Certificate"
2. 2For Firefox: Go to Settings → Privacy & Security → Certificates → Import the CA cert
3. 3For Java apps: Use keytool to import the certificate into the Java keystore
4. 4Restart the application after installing the certificate

Symptoms

• •AI requests bypass the proxy entirely
• •Dashboard shows no requests to ChatGPT, Claude, etc.
• •Sensitive data not being detected in AI prompts

Possible Causes

• •Bleep service not running
• •PAC file not configured in system settings
• •Browser or application ignoring PAC configuration

Solutions

1. 1Verify Bleep is running (check system tray icon - should show green)
2. 2Bleep automatically configures PAC-based routing for AI traffic only
3. 3Restart Bleep if the service stopped unexpectedly
4. 4Note: Only AI traffic (ChatGPT, Claude, etc.) is routed through Bleep - all other traffic goes direct

Symptoms

• •"Failed to connect to license server" error
• •"License not found" error
• •"License expired" error
• •Proxy starts in limited mode

Possible Causes

• •Invalid or expired license key
• •Network connectivity issues
• •Firewall blocking license server
• •License key copied incorrectly

Solutions

1. 1Verify your license key at Dashboard → Licenses
2. 2Ensure internet connectivity to *.supabase.co
3. 3Check if firewall allows outbound HTTPS (port 443)
4. 4Copy the license key again, ensuring no extra spaces
5. 5Contact support if your license was recently purchased

Symptoms

• •AI services (ChatGPT, Claude) responding slowly
• •Timeouts when sending prompts
• •Noticeable delay in AI responses

Possible Causes

• •Complex detection patterns running on large prompts
• •Large response bodies being scanned
• •Resource constraints on the system

Solutions

1. 1Note: Bleep only scans AI traffic - regular browsing is not affected
2. 2Reduce the number of active detection patterns if latency is high
3. 3Check system resources (CPU/RAM) during AI requests
4. 4Large prompts with lots of code may take longer to scan

Symptoms

• •Legitimate content being flagged
• •Non-sensitive data detected as sensitive
• •Requests being blocked unnecessarily

Possible Causes

• •Detection patterns too broad
• •Content matching pattern by coincidence
• •Generic patterns like "key" or "token" matching non-sensitive data

Solutions

1. 1Add false positive domains/patterns to allowlist
2. 2Refine custom patterns to be more specific
3. 3Use context-aware patterns that check surrounding content
4. 4Switch from "block" to "redact" mode for less-critical patterns

Symptoms

• •One app fails while others work fine
• •Application shows network errors
• •Connection refused or timeout errors

Possible Causes

• •App uses custom certificate store
• •App has hardcoded proxy bypass
• •App uses non-HTTP protocols

Solutions

1. 1Check if app has proxy settings and configure them manually
2. 2For Electron apps, set environment variables before launching
3. 3Add app to bypass list if it doesn't need inspection
4. 4Check app documentation for proxy configuration

Symptoms

• •Real-time features not working
• •Chat applications disconnecting
• •WebSocket upgrade failed errors

Possible Causes

• •WebSocket traffic being incorrectly inspected
• •Connection timeout during upgrade

Solutions

1. 1WebSocket connections are passed through by default
2. 2If issues persist, add the WebSocket domain to bypass list
3. 3Ensure the destination uses wss:// (secure WebSocket)

Symptoms

• •Only AI services appear in the dashboard
• •Regular websites don't show up in logs
• •Non-AI traffic seems to bypass Bleep

Possible Causes

• •This is expected behavior - Bleep only monitors AI traffic

Solutions

1. 1Bleep uses selective routing to only intercept AI service traffic
2. 2Traffic to ChatGPT, Claude, Copilot, and other major AI services is scanned
3. 3All other traffic (browsing, email, apps) goes direct without inspection
4. 4This design ensures minimal footprint and no interference with other applications

Symptoms

• •Desktop app shows "Service not running"
• •System tray icon missing
• •Port 8080 already in use error

Possible Causes

• •Another application using the proxy port
• •Previous instance didn't shut down cleanly
• •Insufficient permissions

Solutions

1. 1Check if another proxy is running on port 8080
2. 2Restart the Bleep application
3. 3Run as Administrator if permission errors occur
4. 4Check Windows Event Viewer for detailed error logs

Symptoms

• •Proxy was running but stopped on its own
• •System tray shows proxy is off without user action
• •Error message about license or server connectivity
• •Cannot start proxy - error mentions revocation or server unreachable

Possible Causes

• •Admin server license expired or was revoked
• •Device seat was revoked by an administrator
• •Admin server has been unreachable for over 72 hours
• •Instance conflict - the same license was bound to a different server

Solutions

1. 1Check if the admin server license is still valid in the cloud dashboard
2. 2Contact your administrator to verify your device seat is still active
3. 3Ensure the admin server is online and reachable from this device
4. 4If the server was offline, the proxy will resume automatically once connectivity is restored within the 72-hour grace period
5. 5For instance conflicts, use the rebind option to transfer the license to the current server