Changed to a VPS and now cant access mongodb

[quaint fern]

• Consider reading #how-to-get-help to improve your question!
• Explain what exactly your issue is.
• Post the full error stack trace, not just the top part!
• Show your code!
• Issue solved? Press the button!

[uneven blade]

The IP of your VPS needs to be on your Atlas instance's allowlist afaik

https://www.mongodb.com/docs/atlas/data-federation/tutorial/add-ip-address/

[deft flame]

i can use mongodb but what i mean by that, is that i cannot access the file

to the schemas

const UserProfile = require("../../models/player")
userProfile = await UserProfile.findOne({ discordId: discorid });
                                
MongooseError: Operation playerschemas.findOne() buffering timed out after 10000ms 

and ive set this in mongodb, so that every ip can access it

[ivory zealot]

Have you tried with findOne({}) to make sure it's a connection problem, not a timeout problem?

[deft flame]

no but ill do it wait

[deft flame]

ok this seems to work

i did this

but why cant the other codes do? all i have did is switch to a vps and put the files over there

before the vps it all worked no errors

[ivory zealot]

Then your query is slow as shit, got any indexs?

[deft flame]

you mean array or?

if im right, do you mean something like this?

[ivory zealot]

No an index is a way of finding data fastet in a DB e.g. an Index on Guild Id makes finding all records for a guild faster

[deft flame]

yes, discordId

i would do this to find a profile

[ivory zealot]

Show me your user profile schema

[deft flame]

okay wait

ignore the exp

[ivory zealot]

Yea, you have no index for that schema.
What is discordId, how is it different to userId?

[deft flame]

discordId is the discord id of someone, and userid is from the roblox user

also i can use the findone in my server.js code but not in the other ones, thats weird

[ivory zealot]

I see, you'll want to make both of those an Index as otherwisr your DB is going through every record in the hop to find it in time.

An Index will make it instant

[deft flame]

how do i do that?

[ivory zealot]

guildId: { type: String, index: true },

[deft flame]

okay, let me try

still get the same error

MongooseError: Operation playerschemas.findOne() buffering timed out after 10000ms

i got this error, since ive switched my bot to the VPS

and from the server.js code i can use the .findOne()

[ivory zealot]

But when you tried the "any" find one it worked fine.
So it's got to be a speed problem.

Can you explore the DB in Atllas I assume and make sure tjhe Index has applied

[deft flame]

my code checks if the user has a profile first, using the findOne, if not then it creates a profile for him

but i cant create a profile because the findOne is causing problems

i can use the findOne in the server.js file but not in other code ?

and why? i dont know

[ivory zealot]

What's the other code, where's it live.

And where does server.js live?

[deft flame]

the schema is in the models folder and theres a file called player

and the command is in, commands > verification > verify.js

[ivory zealot]

Well the location of the file shouldn't matter

[deft flame]

why can the server.js file use the findOne tho but the others cant ?

ive ran this code and it worked, but the command cant

[ivory zealot]

I run my Bot on a NodeJS server and that also uses the mongoose code and schemas.

Are your server.js and other files running on seperate places; as in deployed to seperate ones?

[deft flame]

i run the index.js file as same as the server.js

[ivory zealot]

And via both you connect to the DB before you try to make requests?

[deft flame]

no, only the server.js connects to the database

and the other files should be able to use the findOne then

this is only since ive switched to the VPS, if i run them on my computer they work all

i created a new file to test it and it works

but why cant the command use it ???

[ivory zealot]

I assume server.js or something down the line from it imports the files you're speaking of.

What is this sat on, NodeJS?

[deft flame]

yes

nodejs

[ivory zealot]

So the non-server files "can't use it"
Did you try swapping or making a findOne(}} to see if it resolves at all on them.

[deft flame]

i created this file if really only server.js can use it, but this file worked using findOne like i normally do

but the command which im trying to use cant

[ivory zealot]

Ok so everything on the server works fine.
It's just the bot's logic that can't.

But they're run by two different initializations like you said, so the bot's code will also need to connect to the DB, which I assume its doing

[deft flame]

yes its connecting to the database, and i can change/add/find values but the command cant, why?

i didnt change the command since it worked, and now i switched to the vps and it doesnt work anymore

[ivory zealot]

Can you share the command file?

[deft flame]

okay wait

do i just send u the part of it where it tries to do the "findOne"?

or the whole

[ivory zealot]

Do the whole into a pastebin

[digital thicket]

To share long code snippets, use a service like gist, sourcebin, pastebin, or similar instead of posting them as large code blocks or files.

[deft flame]

okay

https://pastebin.com/sqwXPQaD

[ivory zealot]

BTW you can change this:

- const member = interaction.guild.members.cache.get(interaction.user.id);
+ const member = interaction.member;

[deft flame]

alright thanks

[ivory zealot]

So yea the code looks fine, and you tried just putting a find any and it worked in this command yea?
(sorry if already asked, just re-confirming)

[deft flame]

no it didnt work in this command, but in a file ive made for testing the findOne if it really only works in the server.js

@ivory zealot

ive replaced the command code of a older version

and it seems to work but

i get this error:
TypeError: userProfile.save is not a function

and i think the issue was because the "await" did somtehing

[ivory zealot]

Just realised you might habe a major bug, Discord Ids should always be strings, if you ever define them as numbers they will lose precision.

[ivory zealot]

Yea you need to resolve the promise

[deft flame]

okay fixed

[deft flame]

do i add back the await or remove it?

[deft flame]

and this is a new error now

[ivory zealot]

Always need await with promises

[deft flame]

if i add back the await tho, then i cant use the findOne in the command

[ivory zealot]

Well without it you have to reply on horrid .then chaining.

2 secs

Your command function "callback" is async, there should be no reason you can't use await

[deft flame]

ill add back the await and ill check if it still works

TypeError: userProfile.save is not a function
and this came new btw

and yeah, i cant use findOne once i add back await

[ivory zealot]

So here's the problem, you need to resolve promises to ever get data from them, so if adding await causes an issur you must be using save incorrectly.

Also bare with me, I'm on a train

[deft flame]

take ur time

[deft flame]

but the code works without await,

[ivory zealot]

It really shouldn't, least not how you expect.

I see you have

const userProfile = <findOne>;
if (userProfile) {
  //do stuff as record exists
}

Problem is, a unresolved promise is truthy, so even for a missing user profile, it'll run the if

[deft flame]

what should i do then?