#How do you connect mongodb to grasscutter? (typical timeout error and mongo service is running)
47 messages ยท Page 1 of 1 (latest)
I believe native
Can you show your config from grasscutter? Addresses, to be exact
From my experience, it should've worked ootb once you start mongodb
Hmmm, your config looks fine. Any other errors in your grasscutter logs besides connection timeout?
nopers :c maybe i need to install ufw to explicitly allow port?
Iptables, and by extension ufw, by default allow all connections
Does "mongosh" work? Can you connect to db through it?
command works
Grasscutter should create tables by itself
not sure if helpful but mongodb compass doesn't connect to 127 nor using the device's local ip
Yeah, because it is bound to 127.0.0.1, well get to that later
That may be a stupid question by a long shot, but can your pi resolve localhost? In other words, try "ping localhost"
If it doesn't, then just change "localhost" to 127.0.0.1 in your grasscutter config
yeah localhost works, changed all localhost bits to 127, had an apache server running in docker so i changed 443 port in config to 444 but port still in use wtf
Try 8443 or just plain 8080
Let me know if it starts, you'll need to change some other stuff in your config to be able to connect to your server from PC
works ^_^ thnx - disabled docker as well just in case
Ok, that's good.
Now, in your config, you need to disable encryption and change your accessAdress to your pi LAN address
Don't touch mongodb settings, it will work fine
After that you should be able to connect just fine
thanks so much ๐ i'll follow the rest of the git stuff now
No problem, feel free to ask again if you'll have problems
aight so im launching v3.3.0 using cultivation client but server is v3.2.0 and just system errors :VVVVVVVVVVVVVVVVVV .... i heard something about ua patch for 3.2 rsa patch for 3.3 but i have no idea now
read #1025543438604710018
Grasscutter 1.4.3 and above should support 3.3
Either download it from artifacts on github or download the whole package in #resources
And, yeah, you should use RSA patch for 3.3 version of the game, which can be found in resources channel as well
Grasscutter 1.4.3 does not support 3.3. 1.4.5 does.
My mistake, 1.4.4 and above
No worries
1.4.4 doesn't support 3.3 either (only when it was a fork, not official gc), only 1.4.5+ official gc supports 3.3
righteo so i've got 1.4.5 going but keeps java oom errror'ing after plugin setlevel bit... tried setting max 1G/900M but still crashes - is the only way to just run it on a server with more ram?
that should be enough, running with several plugins (although on windows) uses 600mb, if you run it without the plugin is it fine?
it's the default plugins that comes with the zip? i could try remove some stuff if it's unnecessary
not necessary, just was curious since it sounds like you had it running fine before
other than the mongodb issue of course
ah yea 3.2 was apparently working - but client was 3.3 so decided to use diff one
are you sure you don't have any other grasscutters still running in the background somewhere taking up memory or anything
nah I've tried several reboots and disabling docker/apache services
maybe it's because the resources zip was archived to save space, but requires mem to unzip?
I wouldn't think it to be the issue but you can certainly try with it unzipped, you'll just need to make sure you get the folder "Resources" out however many folders deep it is in the zip, then edit config.json so that the line "resources": "./33ResourcesPleaseDoNotExtract.zip", at the top instead reads "resources": "./resources/",
woo! ๐ worked and loads faster when unzipped but had to go from 80443 to lower port because apparently illegal/out of range port.. e: fk i added an extra 0 no wonder