Common Issues

Solutions to the most common problems users encounter.

Authentication Issues

Can't Log In

Symptoms:

• Login fails with no error
• Stuck on login screen
• Redirects back to login

Solutions:

1. Clear browser data:

   Chrome → Settings → Privacy → Clear browsing data
   Select: Cookies, Cached images
   Time range: Last 24 hours

2. Try incognito/private mode:

   • Chrome: Cmd/Ctrl + Shift + N
   • Firefox: Cmd/Ctrl + Shift + P

3. Check email address:

   • Case-sensitive in some cases
   • Look for typos

4. Reset password:

   • Go to forgot password
   • Check spam folder for reset email

5. Check 2FA:

   • If enabled, you'll be prompted for code
   • Use backup codes if you lost your authenticator

2FA Code Not Working

Symptoms:

• 6-digit code rejected
• "Invalid code" error

Solutions:

1. Wait for new code:

   • Codes refresh every 30 seconds
   • Wait for a fresh code

2. Check device time:

   • TOTP requires accurate time
   • Enable automatic time on your device

3. Use backup code:

   • Each backup code works once
   • Generates new codes after

4. Contact support:

   • If locked out with no backup codes
   • Identity verification required

Session Expired

Symptoms:

• Suddenly logged out
• "Session expired" message

Causes:

• Inactivity timeout (configurable)
• Password changed on another device
• Admin revoked session

Solutions:

• Log in again
• Check if password was changed
• Contact admin if issues persist

License Issues

"No Seats Available"

Symptoms:

• Can't start CODITECT
• Error shows seat count

Solutions:

1. Check active sessions:

   • Dashboard → Licenses → View Sessions
   • See who's using seats

2. Wait for release:

   • Sessions auto-release after 6 min inactivity
   • Wait and retry

3. Contact colleague:

   • Ask inactive users to close CODITECT
   • Frees seat immediately

4. Admin force release:

   • Admins can terminate stale sessions
   • Use sparingly

5. Upgrade license:

   • Add more seats in Billing

Session Keeps Disconnecting

Symptoms:

• Frequent "session lost" messages
• License reacquisition required

Causes:

• Network instability
• Firewall blocking heartbeat
• VPN interference

Solutions:

1. Check network:

   # Test connectivity
   ping api.coditect.ai

2. Firewall rules:

   • Allow outbound HTTPS (443)
   • Allow WebSocket connections

3. VPN issues:

   • Try without VPN
   • Whitelist CODITECT domains

4. Browser extensions:

   • Disable ad blockers
   • Disable privacy extensions

License Expired

Symptoms:

• "License expired" error
• Can't acquire seat

Solutions:

1. Check billing:

   • Dashboard → Billing
   • Look for failed payments

2. Update payment:

   • Add new payment method
   • Retry failed invoice

3. Contact admin:

   • Organization owner manages billing
   • May need approval for renewal

Workstation Issues

Workstation Won't Start

Symptoms:

• Stuck on "Starting workstation"
• Timeout error

Solutions:

1. Wait and retry:

   • First launch takes 30-60 seconds
   • Retry if timeout occurs

2. Check quota:

   • GCP quotas may be exhausted
   • Contact support for increase

3. Try different region:

   • Some regions may have capacity issues
   • Change in Project Settings

4. Clear project cache:

   • Project Settings → Advanced → Clear Cache

Workstation is Slow

Symptoms:

• Laggy typing
• Slow file operations
• High latency

Solutions:

1. Check network:

   • CODITECT needs stable connection
   • Minimum 5 Mbps recommended

2. Upgrade machine type:

   • Project Settings → Workstation → Machine Type
   • Try larger instance

3. Close unused tabs:

   • Browser memory affects performance
   • Limit to essential tabs

4. Check project size:

   • Large node_modules can slow things
   • Add to .coditectignore

Files Not Saving

Symptoms:

• Changes lost
• "Failed to save" error

Solutions:

1. Check connectivity:

   • Auto-save requires network
   • Reconnect if disconnected

2. Refresh browser:

   • Force refresh: Cmd/Ctrl + Shift + R

3. Check permissions:

   • Ensure write access to project
   • Check if file is read-only

4. Local backup:

   • Download important files
   • Use git for version control

AI Issues

AI Suggestions Not Appearing

Symptoms:

• No autocomplete suggestions
• AI panel empty

Solutions:

1. Check if enabled:

   • Settings → AI → Enable AI Assistance
   • Toggle on if off

2. Supported file types:

   • AI works with code files
   • Not all formats supported

3. Wait for model:

   • First suggestions may take a moment
   • High load can cause delays

4. Refresh session:

   • Close and reopen file
   • Or refresh browser

AI Responses Are Incorrect

Symptoms:

• Suggestions don't make sense
• Wrong language/framework

Solutions:

1. Provide context:

   • AI works better with more context
   • Include comments explaining intent

2. Be specific:

   • Clear prompts get better results
   • Specify language/framework

3. Use suggestions wisely:

   • Always review AI output
   • AI is a tool, not a replacement

Performance Issues

Browser Running Slow

Solutions:

1. Clear browser cache:

   • Regularly clear cached data
   • At least monthly

2. Disable extensions:

   • Some extensions conflict
   • Try with extensions disabled

3. Update browser:

   • Keep browser current
   • Older versions may have issues

4. Hardware acceleration:

   • Enable in browser settings
   • Uses GPU for better performance

High CPU/Memory Usage

Solutions:

1. Close unused projects:

   • Each open project uses memory
   • Close inactive projects

2. Reduce file watchers:

   • Large projects trigger many watchers
   • Configure .coditectignore

3. Restart browser:

   • Memory leaks accumulate
   • Restart periodically

Network Issues

Can't Connect to CODITECT

Check these:

1. Internet connection:

   curl https://api.coditect.ai/health
   # Should return: {"status": "healthy"}

2. DNS resolution:

   nslookup auth.coditect.ai
   # Should return IP address

3. Firewall/Proxy:

   • Allow *.coditect.ai
   • Allow *.coditect.dev

4. Status page:

   • Check status.coditect.ai
   • May be planned maintenance

WebSocket Disconnections

Symptoms:

• Real-time features not working
• Collaboration issues

Solutions:

1. Firewall configuration:

   • WebSocket uses same port as HTTPS (443)
   • Ensure not blocked

2. Proxy settings:

   • Some proxies don't support WebSocket
   • Configure proxy exceptions

3. Network stability:

   • WebSocket needs stable connection
   • Avoid switching networks

Getting More Help

If these solutions don't resolve your issue:

1. Check Error Codes for specific errors
2. Visit Support to contact our team
3. Include:
   • Browser and version
   • Steps to reproduce
   • Error messages
   • Request ID (if shown)