Since the new satisfactory update they have changed the way ports are used.
New required Port 8888 TCP in update 1.1 should be the only change vs 1.0
Users are unable to connect, and after adding port to firewall and server settings, and even trying to explicitly add 7777 as well, I cannot figure out why its not working.
Reproduction Steps
updated server
added new port 8888 to port forwarding in router
attempted to connect
tried adding 8888 tcp to server settings in amp and attempted reconnectiong, did not work
tried adding 7777 both to server settings in amp and attempted reconnectiong, 7777 shows up as closed
Still working on it, I’ve been tyring for hours, tried at least 10 new instances, and completely removing my old one, default settings, and update of ADS and all instances. some with customized settings and some with default, Still unable to connect
the only consistent thing I see is port 8888 never shows up in the GUI as listening
[Info/1] Port usage for Satisfactory01 (Satisfactory)
[Info/1] Instance is currently running.
[Info/1] LISTENING 8082 TCP (Core.Webserver.Port)
[Info/1] LISTENING 7777 Both (GenericModule.App.Ports.$ApplicationPort1)
And adding it after the fact doesnt work either.
I’ve also tried connecting via lan which doesnt work either.
Yes, I originally tried using the original save, After that failed I backed it up, and just tried to start a brand new game, couldnt get it to connect with the old save loaded, or a brand new game
At this moment I dont care about the save which is why ive wiped and reset it so many times, If it would just work I could figure out the save thing later
In regards to ports and port forwarding, Satisfactory Dedicated Server, launched from steam functions normally.
For this reason, I suspect AMP is not correctly listening on 8888 tcp and I would assume that is the cause of my issue getting people connected to the amp instance.
I am on the latest patch,
ampinstmgr stopall, did a full reinstall, then a repair install since im on windows just in case, and after that I ran ampinstmgr upgradeall just in case.
Yes I had to shut down the satisfactory amp instance to run the Steam version to test.
Just trying to gather more data
When I Mentioned port 8888, it was in regards to the command
ampinstmgr ports
[Info/1] Port usage for Satisfactory01 (Satisfactory)
[Info/1] Instance is currently running.
[Info/1] LISTENING 8082 TCP (Core.Webserver.Port)
[Info/1] LISTENING 7777 Both (GenericModule.App.Ports.$ApplicationPort1)
I figured port 8888 tcp would show up here
It does not show up here or in the GUI
That’s what I’ve been thinking, just didn’t know how to fix it. The amp installer “automatically installed” git, but I will run a quick test and see if its working correctly
thank you for your continued help with this
Git does seem to be functioning via command prompt
I just tried setting up a new instance after navigating to
Configuration-> Instance Deployment → Configuration Repositories,
and using the button “Fetch Latest” from AMPTemplates:main
But the “network port status” Still doesnt show port 8888 tcp on the new instance
do you know where the templates are stored locally on the pc so I can inspect for file directory permission issues?
@Envee Can you do me a favor and check the log to see what messages you see from where you hit that Fetch button to get the latest templates? You can see the logs by clicking the File Manager icon and go into ADS01->AMP_Logs.
[03:08:53] [ADS:GitUser548548 Info/3] : Updating remote source CubeCoders/AMPTemplates:main
[03:08:53] [ADS:GitUser548548 Info/3] : Updating existing remote source https://github.com/CubeCoders/AMPTemplates.git...
fatal: detected dubious ownership in repository at 'C:/AMPDatastore/Instances/ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main'
'C:/AMPDatastore/Instances/ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main' is owned by:
BUILTIN/Administrators (S-1-5-32-544)
but the current user is:
NT AUTHORITY/NETWORK SERVICE (S-1-5-20)
To add an exception for this directory, call:
git config --global --add safe.directory C:/AMPDatastore/Instances/ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main
[03:08:53] [ADS:GitUser548548 Warning/3] : git stash failed on repo CubeCoders/AMPTemplates:main with error code 128
fatal: detected dubious ownership in repository at 'C:/AMPDatastore/Instances/ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main'
'C:/AMPDatastore/Instances/ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main' is owned by:
BUILTIN/Administrators (S-1-5-32-544)
but the current user is:
NT AUTHORITY/NETWORK SERVICE (S-1-5-20)
To add an exception for this directory, call:
git config --global --add safe.directory C:/AMPDatastore/Instances/ADS01/Plugins/ADSModule/DeploymentTemplates/CubeCoders-AMPTemplates-main
[03:08:53] [ADS:GitUser548548 Warning/3] : Failed to update CubeCoders/AMPTemplates:main
Looks like a case of tampering with the permissions at some point. AMP doesnt set the owner to BUILTIN/Administrators. Do you recall ever touching that for any reason?
As far as I can recall, I did not change or adjust any permissions. I’m very much a basic user of AMP, and I haven’t changed or adjusted anything outside of the Instance manager GUI capabilities. If there was any change to those permissions, it was not personally done by me.
If I were to make a guess, since file was supposed to be downloaded by git, If I had previously installed git on the PC, and ran the installer as administrator at the time (before AMP was installed). And somehow that version of git was used during my initial setup of AMP months ago. Then the permission might’ve have gotten out of wack? That would be the only scenario I could think of. But that is just a guess. I don’t have much experience with git or AMP past the most basic usage.
Since my issue wasn’t specifically related to satisfactory, but rather git and downloading templates, I would assume this is just a one-time issue specific to my PC configuration, unless others have an issue like this in the future.
