Connectivity Problem with Satisfactory - cannot connect to server

Technical Support
,
1

System Information

Field Value
Operating System Linux - Debian GNU/Linux 12 on x86_64
Product AMP ‘Callisto’ v2.5.1.8 (Mainline)
Virtualization None
Application Satisfactory
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Issue

installed a fresh instance of satisfactory, i am unable to join remotely or locally. server logs show that the server started up just fine and just prints LogNet: NotifyAcceptingConnection accepted but game reports “Server appears to be offline”. logging in with ssh to server and listing port I can see port 7777 is bound to 0.0.0.0 for both udp and tcp. no firewall rules that i know of, other game server works fine. satisfactory server worked fine before 1.0 update

Reproduction Steps

  • create new satisfactory instance
  • add server in server manager in the game
  • no error message will appear, server is just offline

Discussuion I had in discord:

Have you followed the standard connectivity guide?
_
this one? Diagnosing Connectivity Issues
yes i did
other servers work fine, previous satisfactory version also worked without issues
_
Did you check ampinstmgr dumpfirewall ?
Ah is this a new or an updated instance?
_
this is a new
updated didnt work, so i tried a fresh one
[Info] AMP Instance Manager v2.4.6.6 built 05/10/2023 11:57
[Info] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error] No firewall manager available.
_
You’re on an outdated version of ampinstmgr, and yeah you need a firewall
Update ampinstmgr then run the command again as root
_
so I updated amp to the latest version, still cannot connect. tried my other game servers, everything works fine. I dont understand why I need a firewall for satisfatory 1.0
_
What does ampinstmgr ports INSTANCENAME show when you put in the name of the instance?
_
[Info/1] AMP Instance Manager v2.5.1.8 built 17/09/2024 12:32
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Port usage for Satisfactory01 (Satisfactory)
[Info/1] Instance is currently running.
[Info/1] LISTENING 8081 TCP (Core.Webserver.Port)
_
You need to make a new instance, you’ve had outdated components so the port definitions are missing
Make sure ADS has the latest versions of the templates, and that there are no errors in the console
_
still no port showing in the list. however, when i do the same for e.g. the corekeeper server, it also shows only port 8082, even though i can connect to this server

2

I too am running into this issue as well.

ran: ampinstmgr dumpfirewall and got the following which confirms the instance has ports opened (even confirmed in IPtables that the ports are also opened and able to test connection on the ports too)

Thought maybe it was a missing port and added 15777 and 15000 as custom ports but no change

[Info/1] AMP Instance Manager v2.5.1.8 built 17/09/2024 12:32
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Info/1] Using iptables firewall.
...
[Info/1] TCP/7777 (AMP:THEFACTORYMUSTGROW01:GenericModule.App.Ports.$ApplicationPort1)
[Info/1] UDP/7777 (AMP:THEFACTORYMUSTGROW01:GenericModule.App.Ports.$ApplicationPort1)
[Info/1] TCP/15777 (AMP:THEFACTORYMUSTGROW_101:CustomPort.c5a35af8-623f-451f-a923-8b0f1f2f80b1)
[Info/1] UDP/15777 (AMP:THEFACTORYMUSTGROW_101:CustomPort.c5a35af8-623f-451f-a923-8b0f1f2f80b1)
[Info/1] TCP/15000 (AMP:THEFACTORYMUSTGROW_101:CustomPort.45f212be-db75-4f52-bf10-00b2771e1736)
[Info/1] UDP/15000 (AMP:THEFACTORYMUSTGROW_101:CustomPort.45f212be-db75-4f52-bf10-00b2771e1736)

It worked prior to a few days ago, but only update I did in AMP was the minor patch 20240917.2 so I’m unsure if this is a Satisfactory issue or a AMP issue.

Of note also, the Satisfactory wiki calls for using:

ss -plnu | grep Un

Which should return listing of UDP listening ports but it doesn’t seem to return anything.

on a whim, I tried changing it from the default 7777 port to 17777 and it worked! suddenly i’m able to connect and access the server.

Unsure if this ultimately is an issue on the Satisfactory code (which I’m inclined to think so) or AMP. Seeing as how AMP is adding it to the IP tables and routing properly, i’m thinking this is an issue with the Satisfactory code

3

Create a new instance. The ports were changed to use only 7777 tcp/udp but AMP can’t update ports automatic on existing instances.

4

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.