Connectivity Problem with Space Engineers - Steam port (8766) not listening or open

Technical Support
,
1

System Information

Field Value
Operating System Linux - Ubuntu 24.04.2 on x86_64
Product AMP ‘Phobos’ v2.6.2.0 (Mainline)
Virtualization None
Application Space Engineers
Module GenericModule
Running in Container No
Current State Ready

Problem Description

Steam port (8766) refuses to listen or open

Issue

I can connect using my local IP, unfortunately my use case for the host computer is incredibly jank (it is remaining at my parent’s house while I am at college, and the router we have absolutely refuses to port forward for whatever reason), and I am using playit.gg (a tunneling software) to sidestep the port forwarding issue. AMP works just fine for Minecraft, and I have already checked out the troubleshooting guide and found no solace there. The ports are let through on my linux firewall, and the firewall listed is NOT ufw so that shouldn’t be the issue.

Reproduction Steps

  • Start instance
  • Steam port (8766) and Remote API (8777) not listening in AMP panel
  • Ports 8766 and 8777 listed as closed under response from “ampinstmgr ports”
2

Not uncommon for the steam port not to listen or to be opened only intermittently, unlikely the cause of any connection issue. The remote API port won’t be listening if you haven’t enabled the remote API

If you are trying to connect via the server list, that may not be possible given your public IP is not directly accessible, and the server list would likely be trying to use that

Have you tried connecting via Steam?

3

Hi again! I did find a solution!
For posterity’s sake, and if anyone happens to be using a setup as jank as mine, I’m amending the solution below:

I found this answer on the playit forums here: Setup a Space Engineers Server with playit.gg - guides - playit

Long story short, I opened a tunnel with blank settings and had to set the port in AMP to the automatically assigned port from playit, and it just worked. I guess!
This didn’t open the Steam Port, which as you said isn’t often necessary, the bigger issue was that I couldn’t publicly connect to the server due to the port mismatch and erroneously figured it was because of the other two ports.