-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Access Dashboard - No Error Logs #46
Comments
Hi @jdnielss, |
thank you |
After reviewing the setup, I realized that the DB_URI wasn't properly configured. I'll correct the setup and test again. thanks sir |
when i use Mongodb self hosted, i got this error
already allow my ip in config |
Does this happen only for the backend app or also the frontend? |
this happen only in backend. |
@jdnielss I met the same error when I ran start app:backend, |
I am unable to access the dashboard despite having all the required environment variables set. The application runs without any errors, but I cannot access the dashboard interface.
Environment:
What I’ve Tried:
Expected Behavior:
I should be able to access the dashboard.
Current Behavior:
The dashboard is not accessible, and the app doesn’t log any errors that might help diagnose the issue.
Steps to Reproduce:
Additional Information:
Terminal Logs:
![image](https://private-user-images.githubusercontent.com/28420302/375622242-bd00db9e-baf2-464b-bd6f-386cb9d67ab6.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNDc5NjcsIm5iZiI6MTczOTE0NzY2NywicGF0aCI6Ii8yODQyMDMwMi8zNzU2MjIyNDItYmQwMGRiOWUtYmFmMi00NjRiLWJkNmYtMzg2Y2I5ZDY3YWI2LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDAwMzQyN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTcyZmI2MjgyYWI2ZmM3MGJhYWVjMmYyYjkyYTI2ZmQ2MWZiMmM2MTI1MWVjZGU5MjU1YWQ3NWI1YjQ4OTA0Y2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ovqR8x827pXYzeVikKz4IzbJtPG4JuCiizAi6PuEaf0)
The text was updated successfully, but these errors were encountered: