Skip to content

[Bug]: satisfactory 1.0 unable to launch #4644

Closed
Closed
[Bug]: satisfactory 1.0 unable to launch#4644
Labels
command: startdistro: Debiangame: SatisfactoryIssues related to Satisfactorytype: bugSomething isn't working
Milestone
v24.2.0

Description

@twospheres
twospheres
opened on Sep 10, 2024

User story

as a server admin, I want the server exe to launch and have the correct ports

Game

satisfactory

Linux distro

Debian 12

Command

command: start

Further information

satisfactory 1.0 just launched.
I applied the following fixes to make it run, most of which I guess will be fixed by satisfactory themselves in time, so this is more or less a doc for those that want a manual fix in the meantime.
TL;DR:
-there's a new port TCP 7777, that incorrectly binds to localhost if you use the -multihome flag effectively locking you out from the server.
-They also changed the server executable name that needs new symlinks.

#remove symlink
rm /home/satisfactory/serverfiles/Engine/Binaries/Linux/UE4Server-Linux-Shipping  
#replace symlink to new exe  
ln -s /home/satisfactory/serverfiles/Engine/Binaries/Linux/FactoryServer-Linux-Shipping /home/satisfactory/serverfiles/Engine/Binaries/Linux/UE4Server-Linux-Shipping
#create another new symlink to new exe
ln -s /home/satisfactory/serverfiles/Engine/Binaries/Linux/FactoryServer-Linux-Shipping /home/satisfactory/serverfiles/Engine/Binaries/Linux/UnrealServer-Linux-Shipping

Satisfactory has a new port requirement of TCP 7777. This will give an error when browsing to the server of "failed to connect to the server api"
you must edit your config and remove -multihome ${ip} from the launch flags.
for some reason, when the satisfactory launches with the multihome flag it binds to 127.0.0.1:7777 instead of the multihome IP (or 0.0.0.0).

Relevant log output

No response

Steps to reproduce

No response

Activity

  1. twospheres
    added
    type: bugSomething isn't working
    on Sep 10, 2024
  2. github-project-automation
    added this to LinuxGSM Backlogon Sep 10, 2024
  3. github-project-automation
    moved this to 🆕 New Issues in LinuxGSM Backlogon Sep 10, 2024
  4. github-actions
    added
    command: start
    distro: Debian
    game: SatisfactoryIssues related to Satisfactory
    on Sep 10, 2024

  5. ehcorn commented on Sep 10, 2024

    @ehcorn
    ehcorn
    on Sep 10, 2024

    also can't launch after the new update, get the error: "serverfiles/Engine/Binaries/Linux/UnrealServer-Linux-Shipping" however replacing the symlinks didn't work for me, still says executable not found. Oddly my files are in the sfserver user home directory not in a satisfactory sub-directory so I have a different folder structure to ewildd. I've got a fresh ubuntu 20.04 install that's only setup to run the LGS script.

    edit: Nevermind, I went directly to the folder and fixed launch by replacing the symlinks, launches now. Havent had a chance to test the port issue.

  6. timvandenhof commented on Sep 10, 2024

    @timvandenhof
    timvandenhof
    on Sep 10, 2024

    Same issue here, had to replace satisfactory with the default sfserver to make the symlinks work:

    #remove symlink
rm /home/sfserver/serverfiles/Engine/Binaries/Linux/UE4Server-Linux-Shipping  
#replace symlink to new exe  
ln -s /home/sfserver/serverfiles/Engine/Binaries/Linux/FactoryServer-Linux-Shipping /home/sfserver/serverfiles/Engine/Binaries/Linux/UE4Server-Linux-Shipping
#create another new symlink to new exe
ln -s /home/sfserver/serverfiles/Engine/Binaries/Linux/FactoryServer-Linux-Shipping /home/sfserver/serverfiles/Engine/Binaries/Linux/UnrealServer-Linux-Shipping

    Also had to remove the multihome from the config. After that it seems to work fine, at least on the local network.

  7. svanegmond commented on Sep 10, 2024

    @svanegmond
    svanegmond
    on Sep 10, 2024

    Edit lgsm/config-default/config-lgsm/sfserver/_default.cfg. Change startparameter to read startparameters="FactoryGame -port=${port} -log". Jump ahead to line 160 or so, and change the executable to read: executable="./FactoryServer-Linux-Shipping".

    The lgsm check_executable.sh needs to have the hack for SF update 7 removed from it, the first 'if' clause.

    Further, if your server starts and still cannot connect, there is a bug in the game where if ipv6 is not enabled in your server it will listen to 127.0.0.1:7777 only. Verify this with lsof -ni | grep 7777. The solution is to enable ipv6 in your kernel, then you should see it bound to *:7777. If you can't figure out getting ipv6 enabled in the kernel, use rinetd to forward connections.

  8. FlickyFlack commented on Sep 10, 2024

    @FlickyFlack
    FlickyFlack
    on Sep 10, 2024

    Edit lgsm/config-default/config-lgsm/sfserver/_default.cfg. Change startparameter to read startparameters="FactoryGame -port=${port} -log". Jump ahead to line 160 or so, and change the executable to read: executable="./FactoryServer-Linux-Shipping".

    The lgsm check_executable.sh needs to have the hack for SF update 7 removed from it, the first 'if' clause.

    Further, if your server starts and still cannot connect, there is a bug in the game where if ipv6 is not enabled in your server it will listen to 127.0.0.1:7777 only. Verify this with lsof -ni | grep 7777. The solution is to enable ipv6 in your kernel, then you should see it bound to *:7777. If you can't figure out getting ipv6 enabled in the kernel, use rinetd to forward connections.

    Can confirm this to be working. I've used a clean slate and deleted everything Satisfactory related and did a fresh install using ./sfserver install
    Created the new Symlinks as explained by @timvandenhof (the clean installation does not need to remove the old symlink)
    Also changed the start parameters as explained by you.
    Interestingly, my IPv6 Port did not get mapped and I was still able to join (although it is enabled in the kernel)

    root@<FunnyName>:~# lsof -ni | grep 7777
FactorySe 2404317        sfserver   13u  IPv4 46335836      0t0  TCP *:7777 (LISTEN)
FactorySe 2404317        sfserver   15u  IPv4 46335858      0t0  UDP *:7777

    image
    image

  9. dgibbs64
    added this to the v24.2.0 milestone on Sep 10, 2024

  10. dgibbs64 commented on Sep 10, 2024

    @dgibbs64
    dgibbs64
    on Sep 10, 2024
    Member

    Hotfix now released

  11. dgibbs64
    closed this as completedon Sep 10, 2024
  12. github-project-automation
    moved this from 🆕 New Issues to ✅ Done in LinuxGSM Backlogon Sep 10, 2024

  13. svanegmond commented on Sep 11, 2024

    @svanegmond
    svanegmond
    on Sep 11, 2024

    Yeah, sorry to be unclear, ipv6 needs to be present in OS to provide a ::1 to bind to, even if you don't use it at all.

  14. github-actions commented on Sep 15, 2025

    @github-actions
    github-actionsBot
    on Sep 15, 2025 – with GitHub Actions
    Contributor

    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.

  15. github-actions
    locked as resolved and limited conversation to collaborators on Sep 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    command: startdistro: Debiangame: SatisfactoryIssues related to Satisfactorytype: bugSomething isn't working

    Type

    No type

    Projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions