starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 06:05:57 +03:00

[GH-ISSUE #3649] [BUG] Satisfactory game port parameter changed on last server update - startup parameters need to be fixed #2429

New issue

Closed

opened 2026-02-27 03:02:54 +03:00 by kerem · 11 comments

kerem commented

2026-02-27 03:02:54 +03:00

Owner

Originally created by @0xlord on GitHub (Oct 28, 2021).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3649

Originally assigned to: @johnoclockdk on GitHub.

User Story

As a user, I want Satisfactory startup parameters to be changed so that players are able to connect to the server again.

Basic info

Distro: Rocky Linux 8.4
Game: Satisfactory
Command: ./sfserver start
LinuxGSM version: v20.4.0

Further Information

With yesterdays Satisfactory server update the parameter for the games port changed from -GamePort to -Port. I've updated my common.cfg and it is working again. However this should be fixed within LGSM.
https://satisfactory.fandom.com/wiki/Dedicated_servers

To Reproduce

Steps to reproduce the behaviour:

Install sfserver
Start the server as is
Start the game
Try to connect to the server.
Querry stuff like respond time and game's status are transmitted (server queries), a connection attempt runs into a timed out attempt
Change startup parameter from startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -GamePort=${port} -log -unattended" into startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended" and it works again.

Expected behaviour

Players can join the server again.

Originally created by @0xlord on GitHub (Oct 28, 2021). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/3649 Originally assigned to: @johnoclockdk on GitHub. ## User Story As a user, I want Satisfactory startup parameters to be changed so that players are able to connect to the server again. ## Basic info * **Distro:** Rocky Linux 8.4 * **Game:** Satisfactory * **Command:** ./sfserver start * **LinuxGSM version:** v20.4.0 ## Further Information With yesterdays Satisfactory server update the parameter for the games port changed from `-GamePort` to `-Port`. I've updated my common.cfg and it is working again. However this should be fixed within LGSM. https://satisfactory.fandom.com/wiki/Dedicated_servers ## To Reproduce Steps to reproduce the behaviour: 1. Install sfserver 2. Start the server as is 3. Start the game 4. Try to connect to the server. 5. Querry stuff like respond time and game's status are transmitted (server queries), a connection attempt runs into a timed out attempt 6. Change startup parameter from `startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -GamePort=${port} -log -unattended"` into `startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"` and it works again. ## Expected behaviour Players can join the server again. ![satisfactory](https://user-images.githubusercontent.com/9370461/139250258-f53d6e46-f566-4099-affa-ef8a979a814e.jpg)

kerem

2026-02-27 03:02:54 +03:00

closed this issue
added the
command: install

command: update

command: start

distro: Rocky Linux
labels

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Oct 28, 2021):

Required to be part of the next hotfix

@dgibbs64 commented on GitHub (Oct 28, 2021): Required to be part of the next hotfix

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@freaky-m0 commented on GitHub (Oct 28, 2021):

it seems the server is running on 7778 when you don't change the parameter in the config file. But I don't think that this is helpful to fix it xD Just wanted to give the information here. I had the same error and can connect after I opened 7778 in the firewall (because I spotted this port in the console output)

@freaky-m0 commented on GitHub (Oct 28, 2021): it seems the server is running on 7778 when you don't change the parameter in the config file. But I don't think that this is helpful to fix it xD Just wanted to give the information here. I had the same error and can connect after I opened 7778 in the firewall (because I spotted this port in the console output)

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@johnoclockdk commented on GitHub (Oct 28, 2021):

it seems the server is running on 7778 when you don't change the parameter in the config file. But I don't think that this is helpful to fix it xD Just wanted to give the information here. I had the same error and can connect after I opened 7778 in the firewall (because I spotted this port in the console output)

i guess that a error on you end not lgsm https://satisfactory.fandom.com/wiki/Dedicated_servers

@johnoclockdk commented on GitHub (Oct 28, 2021): > it seems the server is running on 7778 when you don't change the parameter in the config file. But I don't think that this is helpful to fix it xD Just wanted to give the information here. I had the same error and can connect after I opened 7778 in the firewall (because I spotted this port in the console output) i guess that a error on you end not lgsm https://satisfactory.fandom.com/wiki/Dedicated_servers

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@freaky-m0 commented on GitHub (Oct 28, 2021):

it seems the server is running on 7778 when you don't change the parameter in the config file. But I don't think that this is helpful to fix it xD Just wanted to give the information here. I had the same error and can connect after I opened 7778 in the firewall (because I spotted this port in the console output)

i guess that a error on you end not lgsm https://satisfactory.fandom.com/wiki/Dedicated_servers

I don't think so. It worked fine before the latest update and I get exactly the same error (as above) if I close 7778. I will try to change the config file later. Ports are all set to default and there is no forwarding involved. The server is just behind a firewall with it's own public IP.

@freaky-m0 commented on GitHub (Oct 28, 2021): > > it seems the server is running on 7778 when you don't change the parameter in the config file. But I don't think that this is helpful to fix it xD Just wanted to give the information here. I had the same error and can connect after I opened 7778 in the firewall (because I spotted this port in the console output) > > i guess that a error on you end not lgsm https://satisfactory.fandom.com/wiki/Dedicated_servers I don't think so. It worked fine before the latest update and I get exactly the same error (as above) if I close 7778. I will try to change the config file later. Ports are all set to default and there is no forwarding involved. The server is just behind a firewall with it's own public IP.

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@freaky-m0 commented on GitHub (Oct 28, 2021):

I changed the parameter "GamePort" to "Port" in the common.cfg and the server runs at 7777 now. I closed 7778 in my firewall and I can connect as before. Btw the default ports are set in my common.cfg

queryport="15777"
beaconport="15000"
port="7777"

So I think it's related to that problem.

@freaky-m0 commented on GitHub (Oct 28, 2021): I changed the parameter "GamePort" to "Port" in the common.cfg and the server runs at 7777 now. I closed 7778 in my firewall and I can connect as before. Btw the default ports are set in my common.cfg queryport="15777" beaconport="15000" port="7777" So I think it's related to that problem.

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@johnoclockdk commented on GitHub (Oct 28, 2021):

could be how does you startparameter look like

@johnoclockdk commented on GitHub (Oct 28, 2021): could be how does you startparameter look like

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@0xlord commented on GitHub (Oct 28, 2021):

It was changed on the wiki yesterday with the change from 16:14, 27 October 2021‎. It says:

GamePort didn't have any effect. -Port however works. See https://michaeljcole.github.io/wiki.unrealengine.com/Servers_(Unreal_Tournament)/#Required_Ports

Not using -Port parameter seems to increment the standard value of 7777. Bogdan, the server architect at CSS said on Discord earlier (https://discord.com/channels/370472939054956546/902621736602861588/903286943167705169), it is not necessary to set these parameters. But it don't hurt either. That's the explanation, why @freaky-m0 managed to achieve a working server with opening the standardport +1. As well as having the standard port opened up and change the old parameter from -GamePort to -Port.
Doing it the (new) correct way gives the user a standard conform way of setting the server up and doesn't complicate things in troubleshooting for him/her though.

@0xlord commented on GitHub (Oct 28, 2021): It was changed on the wiki yesterday with the change from 16:14, 27 October 2021‎. It says: `GamePort didn't have any effect. -Port however works. See https://michaeljcole.github.io/wiki.unrealengine.com/Servers_(Unreal_Tournament)/#Required_Ports` Not using `-Port` parameter seems to increment the standard value of 7777. Bogdan, the server architect at CSS said on Discord earlier (https://discord.com/channels/370472939054956546/902621736602861588/903286943167705169), it is not necessary to set these parameters. But it don't hurt either. That's the explanation, why @freaky-m0 managed to achieve a working server with opening the standardport +1. As well as having the standard port opened up and change the old parameter from `-GamePort` to `-Port`. Doing it the (new) correct way gives the user a standard conform way of setting the server up and doesn't complicate things in troubleshooting for him/her though.

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@freaky-m0 commented on GitHub (Oct 28, 2021):

could be how does you startparameter look like

the default from the installation/_default.cfg (only -GamePort is changed to -Port now)

startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"

@freaky-m0 commented on GitHub (Oct 28, 2021): > could be how does you startparameter look like the default from the installation/_default.cfg (only -GamePort is changed to -Port now) `startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"`

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@johnoclockdk commented on GitHub (Oct 28, 2021):

could be how does you startparameter look like

the default from the installation/_default.cfg (only -GamePort is changed to -Port now)

startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"

dont change the _default.cfg edit common.cfg

@johnoclockdk commented on GitHub (Oct 28, 2021): > > could be how does you startparameter look like > > the default from the installation/_default.cfg (only -GamePort is changed to -Port now) > > `startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"` dont change the _default.cfg edit common.cfg

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@freaky-m0 commented on GitHub (Oct 29, 2021):

could be how does you startparameter look like

the default from the installation/_default.cfg (only -GamePort is changed to -Port now)
startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"

dont change the _default.cfg edit common.cfg

I know. This IS my common.cfg ;) i copied the values FROM the _default.cfg :D

@freaky-m0 commented on GitHub (Oct 29, 2021): > > > could be how does you startparameter look like > > > > > > the default from the installation/_default.cfg (only -GamePort is changed to -Port now) > > `startparameters="FactoryGame -ServerQueryPort=${queryport} -BeaconPort=${beaconport} -Port=${port} -log -unattended"` > > dont change the _default.cfg edit common.cfg I know. This IS my common.cfg ;) i copied the values FROM the _default.cfg :D

kerem commented

2026-02-27 03:02:55 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Nov 4, 2022):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Nov 4, 2022): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

kerem referenced this issue

2026-02-27 03:55:17 +03:00

[PR #2429] [MERGED] Enable BrainBread steam master server query #3648