Theme
Common Errors
Troubleshooting guide for common issues when using Opensure.
Installation Errors
Chrome Extension Won't Install
Error: "Extension installation failed"
Causes:
- Chrome version too old
- Extension blocked by enterprise policy
- Insufficient permissions
Solutions:
- Update Chrome to latest version
- Check with IT department about extension policies
- Try installing in incognito mode (testing only)
Database Connection Failed
Error: "Failed to connect to Supabase"
Causes:
- Invalid credentials
- Network firewall blocking connection
- Supabase project paused
Solutions:
- Verify credentials in extension settings
- Check network connectivity
- Confirm Supabase project is active
- Test connection using Supabase dashboard
Authentication Errors
Login Failed
Error: "Invalid credentials"
Causes:
- Incorrect email or password
- Account not activated
- Session expired
Solutions:
- Verify email and password
- Check email for activation link
- Request password reset
- Clear browser cookies and retry
Unauthorized Access
Error: "403 Forbidden"
Causes:
- Insufficient permissions for resource
- Wrong tenant context
- CSRF token missing
Solutions:
- Contact admin to verify permissions
- Ensure tenant_id is correct
- Refresh page to get new CSRF token
Data Errors
Policy Creation Failed
Error: "Failed to create policy"
Causes:
- Missing required fields
- Duplicate policy number
- Invalid tenant_id
Solutions:
- Check all required fields are filled
- Verify policy number is unique
- Confirm tenant_id matches your account
Lead Not Saving
Error: "Failed to save lead"
Causes:
- Database write permission denied
- Duplicate lead detected
- Network timeout
Solutions:
- Verify database permissions
- Check if lead already exists
- Retry with stable network connection
- Check browser console for detailed error
API Errors
404 Not Found
Error: "Resource not found"
Causes:
- Invalid URL or endpoint
- Resource deleted
- Wrong environment (staging vs production)
Solutions:
- Verify endpoint URL
- Check resource ID is correct
- Confirm environment matches
500 Internal Server Error
Error: "Server error"
Causes:
- Backend exception
- Database connection lost
- Migration not applied
Solutions:
- Check server status at status.opensure.dev
- Report error to support@opensure.dev
- Include error ID from response
Rate Limiting
Error: "429 Too Many Requests"
Causes:
- Exceeded API rate limit (100 requests/minute)
Solutions:
- Implement exponential backoff
- Reduce request frequency
- Contact support for higher limits
Performance Issues
Slow Page Load
Symptoms: Pages take >5 seconds to load
Causes:
- Large dataset returned
- Network latency
- Browser cache full
Solutions:
- Use pagination for large datasets
- Check network speed
- Clear browser cache
- Disable unnecessary browser extensions
Extension Freezes
Symptoms: Chrome extension becomes unresponsive
Causes:
- Processing too many leads at once
- Memory limit exceeded
- Corrupt extension data
Solutions:
- Reduce batch size to <50 leads
- Restart Chrome
- Reinstall extension
- Clear extension storage
Database Errors
Duplicate Key Error
Error: "Unique constraint violation"
Causes:
- Duplicate policy number
- Duplicate client email
- Race condition in concurrent requests
Solutions:
- Use unique identifiers
- Implement client-side validation
- Add retry logic with exponential backoff
Foreign Key Violation
Error: "Foreign key constraint failed"
Causes:
- Referenced record doesn't exist
- Wrong tenant_id
- Record already deleted
Solutions:
- Verify referenced record exists
- Check tenant_id matches
- Refresh data before retry
MCP Tool Errors
Tool Not Found
Error: "MCP tool 'create_policy' not available"
Causes:
- MCP server not running
- Tool not registered
- Claude Desktop not configured
Solutions:
- Start MCP server:
npm start - Verify
claude_desktop_config.json - Restart Claude Desktop
Invalid Tool Parameters
Error: "Missing required parameter: policy_number"
Causes:
- Required parameter not provided
- Wrong parameter type
- Parameter value out of range
Solutions:
- Check tool schema for required fields
- Verify parameter types match schema
- Review parameter validation rules
Getting Help
Before Contacting Support
- Check this troubleshooting guide
- Review error message carefully
- Note steps to reproduce
- Check browser console logs
- Try in incognito/private mode
Contact Support
Email: support@opensure.dev
Include:
- Error message (full text)
- Steps to reproduce
- Browser/OS version
- Screenshot if applicable
- Your tenant ID (if applicable)
Response Time:
- Critical (P0): 1 hour
- High (P1): 4 hours
- Medium (P2): 1 business day
- Low (P3): 3 business days
Related Documentation
Last Updated: 2025-11-08