You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Images are being added to DB sometimes and when I kill server and start back up the data ojbect with images show up which means in must be connecting and retrieving from mongo
Uri string seems to be fine
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
this is a problem with mongoose itself in 5.10.0. i'm guessing on your yarn.lock or package-lock.json is grabbing 5.10 instead of 5.9.13 because of the ^. you can checkout by running cat node_modules/mongoose/package.json | grep 'version' to see what's really installed. the fastest way to fix this is by in your project's package.json is to pin the version.
cat node_modules/mongoose/package.json | grep 'version' "version": "5.10.0",
you are exactly right
pinned my version to "mongoose": "5.9.13" and it works! thanks!
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 29, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
When adding a pet, post request to mongoose DB seems returns a 500 internal server error
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
Expected behavior
Add pet and return home
Screenshots
If applicable, add screenshots to help explain your problem.
System information
"mongoose": "^5.9.13",
"next": "^9.4.2",
Additional context
Images are being added to DB sometimes and when I kill server and start back up the data ojbect with images show up which means in must be connecting and retrieving from mongo
Uri string seems to be fine
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: