- Check the FAQ section below
- Search existing issues
- Review the documentation
Best for: Questions, ideas, and community discussions 👉 Start a Discussion
Best for: Reporting bugs and issues 👉 Report a Bug
Best for: Suggesting new features 👉 Request a Feature
Best for: Private inquiries, partnerships, security issues 📬 studi.io2907@gmail.com
- Critical bugs: Within 24-48 hours
- General issues: Within 3-5 days
- Feature requests: We review monthly
- Questions: Usually within 1-2 days
Q: I get "Module not found" errors
A: Run npm install in both client and server directories.
Q: MongoDB connection fails A: Check your CONNECTION_STRING in .env and ensure MongoDB is running.
Q: Port already in use A: Change the PORT in your .env file or kill the process using that port.
Q: Login fails with correct credentials A: Ensure your email is verified. Check your spam folder for the OTP email.
Q: Tokens expire too quickly A: Check ACCESS_TOKEN_EXPIRATION and REFRESH_TOKEN_EXPIRATION in .env.
Q: Messages not appearing in real-time A: Check browser console for Socket.IO connection errors. Ensure CORS is properly configured.
Q: Socket connection fails A: Verify ALLOWED_ORIGINS in server .env includes your frontend URL.
Q: Environment variables not working in production A: Ensure all required env vars are set in your hosting platform.
Q: Images not uploading A: Verify Cloudinary credentials and check file size limits (max 5MB).
- Setup Guide: README.md
- API Documentation: README.md
- Contributing Guide: CONTRIBUTING.md
- Code of Conduct: CODE_OF_CONDUCT.md
Join our community:
- GitHub Discussions
- Star the project on GitHub
- Share feedback and ideas
Found a security vulnerability? Please email vimalyadavkr001@gmail.com directly. Do not open a public issue for security concerns.
Need more help? Don't hesitate to reach out! We're here to help. 💚