Skip to content
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

Open
jdnielss opened this issue Oct 11, 2024 · 7 comments
Open

Unable to Access Dashboard - No Error Logs #46

jdnielss opened this issue Oct 11, 2024 · 7 comments
Assignees
Labels
help wanted Extra attention is needed

Comments

@jdnielss
Copy link

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:

NEXTAUTH_SECRET=
DB_URI=mongodb://admin:[email protected]/pm2
NEXTAUTH_URL=http://localhost:3000

What I’ve Tried:

  • Verified that the necessary environment variables are correctly set.
  • Checked the logs, but there are no errors or relevant logs in the application.

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:

  • Set the environment variables as described.
  • Start the application.
  • Attempt to access the dashboard at http://localhost:3000.

Additional Information:

  • MongoDB connection appears to be working as expected.
  • No errors related to NextAuth or MongoDB connection.
image

Terminal Logs:
image

@oxdev03
Copy link
Owner

oxdev03 commented Oct 11, 2024

Hi @jdnielss,
I will try to reproduce your issue today.
BR

@oxdev03 oxdev03 added the help wanted Extra attention is needed label Oct 11, 2024
@oxdev03 oxdev03 self-assigned this Oct 11, 2024
@jdnielss
Copy link
Author

thank you

@jdnielss
Copy link
Author

After reviewing the setup, I realized that the DB_URI wasn't properly configured. I'll correct the setup and test again.

thanks sir

@jdnielss
Copy link
Author

when i use Mongodb self hosted, i got this error


> [email protected] prestart
> tsc --build --clean && tsc


> [email protected] start
> node dist/index.js

/home/ubuntu/apps/monitoring/pm2.web/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185
          const err = new MongooseError(message);
                      ^

MongooseError: Operation `settings.findOne()` buffering timed out after 10000ms
    at Timeout.<anonymous> (/home/ubuntu/apps/monitoring/pm2.web/node_modules/mongoose/lib/drivers/node-mongodb-native/collection.js:185:23)
    at listOnTimeout (node:internal/timers:581:17)
    at process.processTimers (node:internal/timers:519:7)

Node.js v20.18.0
npm error Lifecycle script `start` failed with error:
npm error code 1
npm error path /home/ubuntu/apps/monitoring/pm2.web/apps/backend
npm error workspace [email protected]
npm error location /home/ubuntu/apps/monitoring/pm2.web/apps/backend
npm error command failed
npm error command sh -c node dist/index.js

already allow my ip in config

@jdnielss jdnielss reopened this Oct 11, 2024
@oxdev03
Copy link
Owner

oxdev03 commented Oct 11, 2024

Does this happen only for the backend app or also the frontend?

@jdnielss
Copy link
Author

this happen only in backend.

@codeHessel
Copy link

codeHessel commented Dec 25, 2024

@jdnielss I met the same error when I ran start app:backend,
this is problem is cause by mongoDB can not be connected, u can use some tools to connect your mongoDB.
then mongoDB should be start in replication way

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants