Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Discussions Rules and Guidelines
Report this post
sure... first you need to ask yourself why you want to set up a server :) it's not trivial to do it well and there are many confusing options and a lack of accurate information as so much has been changed over the years and especially in recent months... and providing accurate and helpful documentation in any form is something that Keen have never been good at...
It's interesting the different ways people prefer to find help - in documentation, video or other formats... with something as complex and awkward as the SE server that's poorly documented and even has serious errors and omissions in it's built-in context-sensitive help it's not easy...
Rox may not know how to stop speaking 'backend' lol.
Have you checked out this video?
https://www.youtube.com/watch?v=GxSE_OrikLo
That said, I found another video that may help you :
https://www.youtube.com/watch?v=fMocopAYsDg
+
I recommend to join the SE community to have access to the "help-for-community-server" channel where experienced server admins are helping new admins every days over there.
All can join the SE community from the Discord permalink added to this pinned :
https://steamcommunity.com/app/244850/discussions/0/4622335767039372629/
Once on the Keen Discord -> Go to the Role selection channel to choose PC role to unlock the proper community -> go to the "help-for-community-server" channel to ask for help.
++
Suggestion :
I also recommend to try available servers, a lot are asking to have players every days in the Steam SE Multiplayer sub forum and in the "Sever ads" channel on Keen DIscord, so you could start by helping existing server admins to gain experience before running your own server.
How much friends you have, how much players are waiting to play with you ?
All of you could buy a second copy of SE with a second Steam account to run the server, I can tell it's easier cause it worked right away for me not having experience at all.
EDIT
You can do this without Steam but I never tried, I use the installation steps a) in the Official Guide :
https://www.spaceengineersgame.com/dedicated-servers/
Note - In case you don't know me I must specifiy :
-> I am not a SE Dev but forum Moderator community helper/game tester and I help the SE community since 2013 because it's my Favorite Sandbox game on Steam, and they gave me the [Dev] Tag so I can be admin of the Workshop to help more.
For starters, there's the whole RFC1918 thing: Your home network almost certainly starts with 192.168, and most likely is one of 192.168.1.x, 192.168.0.x, or 192.168.100.x. This is what most SOHO router brands use, and most people don't bother to change from the default.
RFC1918 defines what are known as "private subnets", which are ranges of IP addresses that are specifically defined as "non-routable", which means your ISP will (very correctly) refuse to route them. This is because every IP on the internet must be unique, and every person that bought your brand of router uses the same internal IP addresses.
This is alleviated by what's known as IP Masquerading. This is a technique used by your router to translate each internal IP to its own external IP address when the initial packets for each connection goes out. Since it rewrote the packet, it knows what the return packets will look like and rewrites them so that your internal system can recognize that it's a response that it's waiting for.
Normally this is restricted to connections that are internally initiated, which is why you had to open up a port on your firewall. When you do that, the firewall listens on that port on its external interface and does the same type of rewriting it would do as if it were receiving a response to a connection made by that internal system you told it to send those packets to (oversimplified, but I think that should explain it).
This is all needed information for the next part to make sense.
If you configured your SE server to advertise its internal IP address (the one in the 192.168.x.x subnet), only something on your internal network will be able to see or reach it. This is likely why it shows up in your LAN list (Local Area Network).
If this is the case, you need to reconfigure the SE server with your external IP address (as the rest of the world sees it). Note that this is likely not your router's external IP address, but what's upstream of that (depending the approach your ISP uses). You can find the IP you need to use by using various sites found using the google search "what is my ipv4 ip". Note that you almost certainly want to use an IPv4 IP address and not an IPv6 IP address as the latter massively complicates things. An IPv4 IP address looks like what I described above. If yours has letters and colons instead of only numeral digits and decimals, then that's an IPv6 address and you need to find out your IPv4 address instead (it will be a set of exactly 4 numbers between 0-255 separated by decimals).
This is where it gets ugly.
It is entirely possible that you're behind what's known as a CGNAT (Carrier-Grade Network Address Translation). That basically means that there is another layer of IP Masquerading going on that's out of your control. Your only option if this is the case is to pay extra money to your ISP for a static IP address.
Yes, I am prepared to help, which is why I sent you a Steam friend request at the same time as my first post to this discussion ^.^
... and two birds... I assure you, sir, I can speak backend, frontend, top and bottom :P
1. Setting up the dedicated server software and getting it working correctly.
2. Forwarding ports in your router so that others outside of your LAN can not only see your server, but join it as well.
It is STRONGLY recommended that you DO NOT run your dedicated server software on the same machine that you play on.
This can, and often does, create issues for both you and the server itself.
Any spare PC that is less than about 10 yrs old is capable of running the dedicated server software as it is only code, and NOT graphical. You don't even need a good video card to run a dedicated server.
The vanilla DS software that you get through Steam is a bit clunky, but functional.
There is no real GUI for it and you have to constantly look up what parameters that you need to set to make it functional. I recommend TorchAPI[torchapi.com]. I've been running this on my dedicated server and it's much easier to work with than the vanilla software.
The next big thing is making sure that you have ports forwarded to your server PC.
For this reason, it is advised that you DO NOT use a wireless connection from your server PC to the router. Connect it directly to the router via a network (CAT5) cable.
The reason for this is simple, you want the most reliable connection that you can get, and frankly, wired is leaps and bounds more reliable than WiFi.
You can connect to your server via your gaming PC wirelessly if you like, though I wouldn't recommend it.
There's a second reason for doing this wired, this allows you to assign a LAN IP address to your server PC for the port forwarding in the router to work correctly.
Port forwarding only works with a dedicated IP address to forward the ports to.
You assign your DS computer an internal IP (LAN) address from within Windows, which is pretty standard and can be looked up almost anywhere, but routers, where the port forwarding happens, are varied due to differences in manufacturer and the firmware of the particular brand and model of router that you have.
You will have to look up port forwarding for your specific router in order to do it correctly.
So, in a nutshell:
1. Connect the DS computer to your router with a network cable.
2. Assign the DS computer an internal LAN IP address.
3. Access your router and forward the necessary ports to your DS computer's LAN IP.
4. Install the DS software and set it up how you want the server to run.
5. Open SE on your gaming PC and create a world for your server.
6. Copy that world to your server.
7. Run the DS software and enjoy.
Only catch under ubuntu is that I could only make it run with the -noconsole flag which means manually configuring everything. Easy enough to do that on your windows computer and copy the save over.