I cant connect to server after leaving it.

[Geskawary234]

Even if i reaload server nothing changes! I dont change config files or anything. Maybe issue with my internet cuz i experience the same with some servers too. My server is hosted on debian10 machine with 2 cores 8 gigs of ram, i also have normal minecraft 1.20.1 server running, so i set not 25565 port but 25566 port, can that matter?

[Geskawary234]

Also where can i limit resources which are dedicated to the server

[rdebath]

It can run on port 25566 no problem.

• What does "cant connect" mean? Are you connecting to localhost 25566, looking it up in the sever list, trying to use the wrong client or something else?
• Are there any error messages on the client?
• Are there any error messages on the console?
• Are there any error messages in logs/errors/*.log
• Is the connection attempt logged in logs/*.log
• Is the process still running: Probably see with this ps -f -C mono-sgen or ps -f -C mono
• Is it responding: printf "\0\7%-64s%-64s\0" '+' ''|nc -v localhost 25566 |cat -v;echo should give connection succeeded and ^NInvalid player name

Are you using a VPS? Do you need to tunnel your classicube login: ssh -L 25566:127.0.0.1:25566 vps1234.provider.game

---

Resource limitation is a dfferent issue, it has to be done at the mono or OS level, for example: Memory limit: export MONO_GC_PARAMS=max-heap-size=1536M Memory limit: ulimit -v 1572864 CPU Cores: taskset -c 0 mono MCGalaxyCLI.exe CPU Percentage: cpulimit ...

MCGalaxy is pretty happy with one (small) core and 1G ram. Large maps need more ram than this with the largest needing 4G just for one map (Each loaded museum map also needs same memory as a normal map)

Note: Usually MCGalaxy will catch out of memory errors, however, if you limit the memory of mono (by either method) it may (sometimes) hard crash rather than it's usual "swapping the system to death" crash method. This is probably a good thing but does mean you need an automatic restart from something else.