Troubleshooting
Common issues and solutions when working with the Couchbase module.
Common issues and solutions when working with the Couchbase module.
🚨 Connection Issues
Cannot connect to Couchbase
Symptoms:
Error: Timeout during bootstrapSolutions:
Verify Couchbase is running:
curl -u Administrator:password http://localhost:8091/poolsCheck connection string:
// Single node
"connectionString": "couchbase://localhost"
// Multiple nodes
"connectionString": "couchbase://node1,node2,node3"
// Secure connection
"connectionString": "couchbases://cluster.example.com"Verify credentials:
Check firewall rules:
Port 8091: Management/REST API
Port 8093: N1QL Query
Port 11210: Key-Value operations
Connection timeout errors
Symptoms:
Solution: Increase timeout values:
🗄️ Bucket/Collection Issues
Bucket not found
Symptoms:
Solutions:
Verify bucket exists in Couchbase:
Create bucket if needed:
Via Couchbase Web Console (http://localhost:8091)
Or via CLI:
Check bucket name in config:
Scope or collection not found
Symptoms:
Solution: Create scope/collection or use defaults:
🔐 Authentication Issues
Invalid credentials
Symptoms:
Solutions:
Check username/password:
Verify user has permissions:
Use environment variables for security:
📝 Query Issues
N1QL query errors
Symptoms:
Solutions:
Escape bucket names with backticks:
Use proper collection path:
Use parameterized queries:
Index not found
Symptoms:
Solution: Create a primary index:
🤖 Vector Search Issues
Vector search returns no results
Solutions:
Verify vector index exists:
Create vector index if needed:
Check embedding dimensions:
Verify documents are stored correctly:
Low similarity scores
Solutions:
Use same embedding model for storage and search:
Improve query quality:
Adjust result limit:
🗄️ Session Storage Issues
Sessions not persisting
Solutions:
Verify session storage is configured:
Check cache name matches:
Verify Couchbase is accessible:
⚡ Performance Issues
Slow cache operations
Solutions:
Check network latency:
Increase connection pool:
Use appropriate timeouts:
Monitor with statistics:
High memory usage
Solutions:
Set appropriate TTLs:
Use cache eviction:
Clear old data:
🐛 Debugging Tips
Enable debug logging
In boxlang.json:
Check Couchbase logs
Test connectivity
📞 Getting Help
If you're still having issues:
Check logs - Enable debug mode and check BoxLang and Couchbase logs
Verify Couchbase health - Use Web Console (http://localhost:8091)
Test isolation - Create minimal reproduction case
Community support - Post on Ortus Community
Professional support - Ortus Solutions Support
🔗 Useful Links
Last updated
Was this helpful?
