-
-
Notifications
You must be signed in to change notification settings - Fork 211
Troubleshooting
Huy Nguyen edited this page Apr 5, 2025
·
1 revision
Note: This troubleshooting guide is under active development and will be expanded with more comprehensive solutions soon.
This guide provides solutions to common issues that may arise when installing, configuring, or operating Mixcore CMS.
- Installation Issues
- Database Connectivity
- Authentication Problems
- Performance Issues
- Module and Service Integration
- Deployment Challenges
Symptoms:
- Application fails to start
- "Unable to start Kestrel" error message
Possible Causes:
- Port conflicts
- Missing dependencies
- Improper configuration
Solutions:
- Check if another application is using the configured ports
- Verify that all required dependencies are installed
- Review appsettings.json for configuration errors
Symptoms:
- Migration errors during startup
- Database tables not created
Possible Causes:
- Database connection issues
- Insufficient privileges
- Conflicting migrations
Solutions:
- Verify database connection string
- Ensure database user has appropriate permissions
- Check migration history for conflicts
Symptoms:
- "Connection refused" errors
- Timeout when connecting to database
Possible Causes:
- Database service not running
- Incorrect connection string
- Network/firewall issues
Solutions:
- Verify database service is running
- Check connection string parameters
- Confirm network connectivity and firewall rules
Symptoms:
- Authentication failures despite correct credentials
- Redirect loops during login
Possible Causes:
- Cookie issues
- Cache problems
- Authentication configuration issues
Solutions:
- Clear browser cookies and cache
- Verify authentication settings
- Check identity configuration
Symptoms:
- Pages load slowly
- API requests take long to complete
Possible Causes:
- Inefficient database queries
- Missing indexes
- Insufficient resources
- Lack of caching
Solutions:
- Optimize database queries
- Implement proper indexes
- Increase system resources
- Configure caching
Symptoms:
- Modules fail to load
- Missing functionality
Possible Causes:
- Dependency conflicts
- Incompatible versions
- Improper configuration
Solutions:
- Check for dependency conflicts
- Verify module version compatibility
- Review module configuration
Symptoms:
- Container fails to start
- Services unavailable
Possible Causes:
- Missing environment variables
- Volume mounting issues
- Network configuration problems
Solutions:
- Verify environment variables
- Check volume mounts
- Review network configuration
If you encounter issues not covered in this guide, please:
- Check our Community Forum for similar issues
- Report the problem in our Issue Tracker
We are actively expanding this troubleshooting guide. Your feedback helps us improve!