I stood up a Satisfactory dedicated server in Docker 2026-01-17 Game Server v1 - Satisfactory.

Another buddy wants access and Mods were requested.

I thought I should probably take security a bit more serious and only give them access to the game ports. I could be far more secure, but this is a great start and a minimum.

I haven't gotten mods working yet

Customizable Awesome Additions - SMR

I broke both of their's access

Somehow the session was set to “just me”. Not sure how this all happened?

ACLs I think are working, unless they are contributing to the breakage mentioned above

I did setup a Tailscale tag per AI’s recommendation - you reference a tag not the hostname/IP of the target machine. More stable.

Not sure if all these ports are needed but I couldn’t get it to work otherwise. They connect via the server manager so I kept 8888.

"grants": [
		{
			"src": ["friend1@gmail.com", "friend2@gmail.com"],
			"dst": ["tag:game-server"],
			"ip": [
				"udp:7777",
				"udp:15777",
				"tcp:8888",
				"udp:15000",
				"tcp:7777",
				"tcp:15000",
				"tcp:15777",
			],
		},
		{
			"src": ["my-email@gmail.com"],
			"dst": ["*"],
			"ip":  ["*"],
		}
	]

Here is the original ACL I had before adding rules:

Changing Session Type Crashes Game

I have to go to single apply go to game. Then just choose IP, go to game. Giving a session name crashes the game.

Nice to haves

  1. SSL - Since I have 2026-01-11 DNS setup nginx proxy manager I could expose securely.