So I completely removed AMP and reinstalled with Container activated, then reinstalled both Valhiem and two instances of Satisfactory.
All instances started and attempted to access from client… all fails.
I have opened seperate ports on the modem to each instance, but the Satisfactory Client shows server off-line and the Valhiem Server, while displaying playfab as active in the client will not connect.
What am I missing?
@CubeCoders-Bot can you walk the user through verifying connectivity to their server please? They’ll be using host mode networking so just check ports/firewall on the host system.
threeguys@3guysgame:~$ ampinstmgr ports [ValheimI01]
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] No such instance matching name: ‘[ValheimI01]’
Status
Satisfactory2 (Satisfactory201)
threeguys@3guysgame:~$ ampinstmgr ports [Satisfactory201]
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] No such instance matching name: ‘[Satisfactory201]’
Alright, so your ports are open, but it looks like there might be an issue with how the instances are being referred to. Let’s try the ampinstmgr ports command again without the square brackets:
threeguys@3guysgame:~$ ampinstmgr ports ValheimI01
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] No such instance matching name: ‘ValheimI01’
threeguys@3guysgame:~$ ampinstmgr ports Satisfactory201
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
[Error/1] No such instance matching name: ‘Satisfactory201’
threeguys@3guysgame:~$ ampinstmgr list
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
Looks like Docker is throwing an error. Let’s first check if Docker is running properly. Run:
sudo systemctl status docker
If Docker isn’t running, start it with:
sudo systemctl start docker
Next, let’s see if there are any issues with the Docker containers used by AMP:
sudo docker ps -a
This will list all Docker containers and their statuses. If any containers have errors, you might need to inspect them for more details. You can do this with:
sudo docker logs [container_id]
Replace [container_id] with the actual ID of the container.
Check these and let me know what you find!
This post was produced by an AI controlled by CubeCoders Limited - Feedback
Docker seems to be up and running, but there’s an issue with AMP recognizing the instances. Let’s try refreshing AMP’s instance list and then attempt to list the instances again.
Refresh AMP instance list:
ampinstmgr --nocache list
If still no luck, let’s re-sync the instances:
ampinstmgr --sync
List the instances again:
ampinstmgr list
Run these commands and let’s see if AMP can properly recognize the instances now.
This post was produced by an AI controlled by CubeCoders Limited - Feedback
threeguys@3guysgame:~$ ampinstmgr --sync
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
AMP Instance Manager
Syntax: ampinstmgr [Flags] [Operation] [Arguments] (Optional Arguments)
Available Flags:
–nocache : When creating/updating instances, do not use an existing cached copy of AMP
–silent : Suppresses all output
–advanced : Show advanced operations when using the help command
–docker : When creating/starting instances, start the instance inside a Docker container (requires root or a user with docker access)
-version : Display the version and exit
Available Operations:
–BrowseInstance [Instance Name]
Browse to an instance
–ChangeInstanceStream [Instance Name] [Release Stream] (Force)
Switch an instance to a different release stream
threeguys@3guysgame:~$ ampinstmgr --nocache list
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
threeguys@3guysgame:~$ ampinstmgr --sync
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
AMP Instance Manager
Syntax: ampinstmgr [Flags] [Operation] [Arguments] (Optional Arguments)
Available Flags:
–nocache : When creating/updating instances, do not use an existing cached copy of AMP
–silent : Suppresses all output
–advanced : Show advanced operations when using the help command
–docker : When creating/starting instances, start the instance inside a Docker container (requires root or a user with docker access)
-version : Display the version and exit
Available Operations:
–BrowseInstance [Instance Name]
Browse to an instance
–ChangeInstanceStream [Instance Name] [Release Stream] (Force)
Switch an instance to a different release stream
–UpgradeInstance, -u [Instance Name] (restart If Running)
Upgrade an existing AMP instance in-place
–ValidateInstance [Instance Name]
Check the integrity of an instances files
–Version
Display the version
–View [Instance Name] (Force)
View the console of a running AMP instance
threeguys@3guysgame:~$ ampinstmgr t
[Info/1] AMP Instance Manager v2.5.1 built 06/07/2024 22:14
[Info/1] Stream: Mainline / Release - built by CUBECODERS/buildbot on CCL-DEV
threeguys@3guysgame:~$