Daniel86268

Often asked, just as many times answered: It's a general bug that sometimes happens. For some people port forwarding fixes it, for others it doesn't. Even Klei's servers have that sometimes. (Most noticeably during an event such as Forge or Gorge.) I had the issue myself for a while, but never really bothered trying to fix it, and at some point it suddenly fixed itself for no apparent reason.

You are missing your token on your cloud server.

First of all, the config files do seem correct to me. Now to the issue: I sometimes get a similar error, when the Caves Shard was booted up before the Master Shard. Not sure why, but the DST server sometimes has issues connecting them in that situation. Try starting the Master Shard up first completely and afterwards the Caves Shard, and see if they connect then.

Just go into the save folder of the server you have as a slave and then add return { override_enabled = true, preset = "DST_CAVE", } to the .klei/<server_name>/<cluster_name>/Caves/worldgenoverride.lua. Afterwards regenerate that map. Then it should generate a caves map.

As the log says that the port it's trying to use is in use, either stop the software that is using the port or set a different one for the server to use.

That is still very possible as it was years ago. It's just some extra work and not just start up running out of the box. Either take a look here, and/or use the shard configuration mod. All in all, the DST server is neither more nor less limited as it was years ago.

I think the easiest steps of tracking down the issue would be first to read the server log, or alternatively the client log if the server log doesn't show anything. It might show something the moment the client disconnects, such as a bad packet or whatever disrupts the data flow. If that doesn't point you to any solution try starting a fresh map without any mods and see if the issue persists. If it's working fine then it's probably either some incompatibility between mods or maybe a mod that is incompatible with one of the recent DST updates. If that still has issues, I guess the only way to actually track down the issue would be actually analysing the traffic with wireshark or a similar tool. Though in that case it'd probably easier to actually just set up a dedicated server and hope that it'll somehow fixes the issue xD.

A ~1 sec spike won't be nearly enough for a complete timeout. A friend of mine sometimes plays with a second delay constantly, spiking to something like 5-20 seconds delay (due to long distance and internet things) without disconnects. While it is possible that a dedicated server can fix those issues, I'd first try to track down the initial cause for those timeouts: Are you running any mods? Are there any mods on the host? Is the Host hardware good enough? Does the host have internet disconnects once in a while? etc. Cause afaik the dedicated server doesn't have any option for prolonging the time till disconnect. Also the client hosted ones shouldn't disconnect you as quickly as that without reason either. So you've probably got timeouted due to a different reason, possibly one of the ones I've listed above.

Processing power is generally counted in teraflops. 4 Gigabytes is a unit of measurement for storage, in that regard: RAM. Same as saying "My car has a range of 1200 kilograms". Back to topic, I agree that DST should either switch over to 64 bit or have a second 64bit version like starbound. Only "problem" would be that a 64 bit program generally needs a bit more space, since some variables and numbers end up being larger. And ofc, lots of more work for Klei. As long as you use the same protocols (What you would usually do) there's no communicative difference between a 32 bit DST and a 64 bit, so the server wouldn't even notice without an extra parameter if a client is 32bit or 64 bit. Edit: On the other hand it very rarely happens that someone actually runs over the limit. I've only seen once that someone hit the memory limit with a >70 days map and like literally 86 mods.

Looking at the log the server is looking for the file " /lib/libcurl-gnutls.so.4", so maybe a link from /usr/lib/libcurl-gnutls.so.4 to /lib/libcurl-gnutls.so.4 might fix things. If there's already a link there, the issue might be that you possibly have the 64 bit version installed, yet the DST server is a 32bit application, and needs the 32bit libcurl-gnutls.so.4. (Not entirely sure about this one though, since it's been a long time since I've set up a server myself.)

Of course. I might not be able to answer immediately, since I'm not on the forums all day long, but I'll answer eventually.

This probably just printed the like you gave it, since you directed it to a file, and not a directory. Try either whereis libcurl-gnutls.so.4 This should print where the object is, if it is installed on the system. As you are apparently running an ach system, you might be using the packet manager pacman. If so, you can install the package like this: pacman -S libcurl-gnutls.so.4 (You might have to run a "pacman -Syu" before to update your system, because that's how arch works.) I ran into the issue once, that the server didn't find the library despite it being properly installed. I fixed this by linking the library to the location the DST server is looking for.

First of all: Don't force enable mods. That can break things, and unless you are developing a mod atm, it's not recommended. [00:00:00]: WARNING: Force-enabling mod 'workshop-356435289' from modsettings.lua! If you are not developing a mod, please use the in-game menu instead. [00:00:00]: WARNING: Force-enabling mod 'workshop-398109522' from modsettings.lua! If you are not developing a mod, please use the in-game menu instead. [00:00:00]: WARNING: Force-enabling mod 'workshop-478005098' from modsettings.lua! If you are not developing a mod, please use the in-game menu instead. [00:00:00]: WARNING: Force-enabling mod 'workshop-553670059' from modsettings.lua! If you are not developing a mod, please use the in-game menu instead. [00:00:00]: WARNING: Force-enabling mod 'workshop-866623002' from modsettings.lua! If you are not developing a mod, please use the in-game menu instead. [00:00:00]: WARNING: Force-enabling mod 'workshop-1207269058' from modsettings.lua! If you are not developing a mod, please use the in-game menu instead. The problem itself seems to be your save file though, as it is corrupt: [00:00:05]: [string "scripts/saveindex.lua"]:308: Corrupt Save file [session/E606613D9F6C9BE5/0000000003] Try deleting it and see if it works then. (after you enabled the mods the proper way using the modoverrides. For that you can check out my guide on mods on dedicated servers.)

It's actually very simple to host multiple dedicated servers on one machine. Probably so simple that noone bothers to write about it. You just have to create mutiple cluster folders with the individual server configurations and ports, and then launch them with individual start scripts pointing towards the designated cluster folders. You can use the same dedicated server files as well, so no need to redownload it either.

For me it's working on Manjaro (a variant of Arch linux), and it's working perfectly fine for me. Can you try to add -validate to your steamcmd command?