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
Sorry i didnt see this message b4 i saw ur friend request, i sent one to u. Please send again.
I accepted your friend request, message me when u want to talk.
The setup was easy and the server is running with awesome ping time. Latency with Steam is around 30 to 40. Average ping time to the server while playing has been 22 to 25.
For updates and backups, i run my own custom powershell scripts that run hourly to scan for an update availability.
I had a script that saved hourly as well but disable dit for now as the auto save feature built in is not able to be turned off currently
Edit: Just read the sticky and Linux is supported!
The easiest way to do this is to simply get a proxy service. It will forward game traffic to your server(s), and block the rest. AWS is pretty resilient as-is (and with proper planning/setup can be amazing - but that's if you know what you're doing), but again, one misstep and you're paying hundreds (possibly more) for one month. That's a costly mistake, especially when an anti-DDoS service costs ~$15 per month.
Just an FYI.
If you don't go with the added cost, at the very least make sure ONLY your game traffic ports are open, change your remote desktop/ssh port from the default to something only you know, and block the query port so only a few IP addresses can query your server (like Steam, the Master Server List, TopArkServers.com, etc.). These steps alone will make a DDoS attack pretty unlikely (but not impossible). They'll also help make hijack attempts (via brute force) a bit less likely, though making sure you protect your Linux instance with a public + private key and your Windows instance with a very complex RDP password is always advisable.
To be perfectly honest, this is why game hosting companies charge what they do. To get everything setup properly, and staying on top of prospective exploits/attacks, is often a pain in the ass. It's not just setting up a server, it's a tremendous amount more work than that. Setting up the server is the downright easy part.
PS. I'm not sure what your guide contains, but I hope it includes setting up a reserved IP address instead of just setting up an instance and calling it good. Otherwise, the IP may change, and players will instantly be unable to join without finding the server again.
Ooohhh, thanks so much for that advice!