Talk:Dedicated servers

I'm thinking sequencing the sections might be wise; they seem kind of scattered right now. I suggest: - Summary - Requirements - Steam/SteamCMD installation - Starting the Server - Initial Setup / Configuration - Port Forwarding / Firewall - Running as a Service - Docker - Automated install / Server manager options - Common errors - History

PhonicUK: Running as a service should probably be its own page since there are so many options. That section alone accounts for a lot of clutter. The system requirements should also be a nicely formatted table.

itzhayleyuk: I agree with the point by PhonicUK, also it might be worth a mention, that for SystemD configurations to work - at least for me on CentOS - SELinux needs to be disabled.

CubGeek: Good idea on breaking things into a more logical sequence, thank you! I would also agree that Running As A Service likely needs to be split off to it’s own page, with sub-sections for the various distros and OS flavors

DopeGhoti: Thanks for the feedback. I've done a first pass on re-ordering the main page and broken out Running as a Service to its own page.

Potential new system reqs table:

DopeGhoti (talk) 09:49, 2 November 2021 (UTC) I like it.

> You do not have permission to edit this page, for the following reason:

> This page has been protected to prevent editing or other actions.

Why tough? Were there a edit war? This is gatekeeping and doesn't do any good besides a selected circle of few.

So far as I know, only anonymous editing is blocked right now. Create a free account and you can freely contribute. DopeGhoti (talk) 05:47, 4 November 2021 (UTC)

Yes there was an edit war and we have only blocked anonymous users, simply make a free account to make edits or suggest the edits here in the talk page and someone will likely add it for you. Also keep in mind this block is not permanent and will expire in a few weeks. 15:25, 4 November 2021 (UTC)

You might add a some advice:

If you're getting errors about being unable to bind to 0.0.0.0:15777, trying using the -multihome option -multihome, where is the ip address of your home system (ex: sh FactoryServer.sh -multihomme=192.168.0.5 )