Enshrouded | Server not visible via extern ip

Technical Support
1

OS Name/Version: Ubuntu Server 24.04.2

Product Name/Version: AMP 2.6.1.6 / Enshrouded build 697669

Problem Description: Can’t connect via extern ip. However, can invite via steam friend list?

Steps to reproduce:

  • Install default enshrouded instance
  • Change password for usergroup in .json
  • Can’t see server in Browser

I just created the default instance and changed the password in the servers .json file.

Wether i nor other people can see my server in the ingame server browser.
You also cannot add the server via the View–>Game Server option in Steam.
I can connect however from my windows gaming setup via my local ip and then use the invitation function over the steam friend list. How strange is that.

Sadly the server won’t be added in the “recent” history of the external players. So they can’t connect afterwards without another steam invite.
All the neccessary ports are opened via ufw allow in udp and tcp. I also configured my router.
I also had the same issue in valheim where connection via extern ip was not possible.
I then manually installed a few packages mentioned in the dedicated server setup article from the official website, which then resolved the issue and made the server connectable.

I also googled for required packages for enshrouded and installed them, but had no luck yet.

1 Like
2

Also encountering this issue. Issue still exists with server version 698915.

Noted in the logs, at least for me, is an invalid state transition in the state machine controlling Steam server status provision:
[OnlineProviderSteam] started transition from 'Uninitialized' to 'Initialized' (current='<invalid>')!

Could you please list which packages you added or provide a link to the article? I’m inclined to believe that there is something with Wine or Proton that’s interfering with it and maybe there’s a dependency that could help or point to an underlying issue.

I’ve been fussing with it for a week and haven’t been able to connect to it at all, local IPs or otherwise.

3

Comment from someone in the Enshrouded discord:

if you want to Test connections from the outside, use our Query Tool: https://esquery.suhosting.net/ -- second, I'd reccomend adding the server via IP, in game or in Steam Server list -- searching for Server name isn't great

4

Same issue here, also hosting on a Ubuntu maschine

5

If you want to see if it is networking issues at your end, try my server:

168.138.13.215:15637

If you can connect to that, then you know it’s something at your end (NAT hairpin, port forwarding, CG-NAT, firewall, etc).

6

I can join that, I also have a VRising server and that one works with no issues so I figured that there was something wrong with Enshrouded

7

Games can have different connection methods - what works for one, doesn’t necessarily work for another.

Can someone outside your network connect to your server? If so, it points to a NAT hairpin issue for you

8

Sorry for my late response.
The packages i downloaded which made my valheim server function were:
libatomic1
libpulse0
As i said i got them from the official valheim dedicated server guide A Guide to Dedicated Servers - Valheim

The server is able to connect to other servers, the issue is the other way around, at least with enshrouded. I also have issues with vintage story. I got to run factorio and valheim on the server.

I’ll be visiting my folks this weekend and take the server with me. If the servers will work on the new network i guess i’ll know it’s the router or the isp.

9

Other people can connect over the steam friends list without issue but not through the IP, I can join the server just fine via my home network

10

Those packages for Valheim are to ensure crossplay functions. Not relevant to Enshrouded.

Not sure what you mean by “server is able to connect to other servers”. That’s not a thing. Clients connect to servers.

11

You sure they are using the right IP? External folk need to use your public IP.

12

Yeah ive been using the external IP4 that shows up in the console after server start and also shows up on “Whats my IP”

13

You’re also using the public IP when connecting from within the same network as the server?

14

No im using the internal one, it also shows up in my server list but no one elses

15

Sounds very much like a port forwarding issue then

16

I am out of Ideas, ports are forwarded both UPD and TCP I also tried to use a different port but ive got no success

17

Sorry i refer to my machine as a server. I meant that my machine is able to connect outwards, as a client to other servers.

18

Well, that’s pretty normal. The default on most systems and routers is to allow all outbound traffic by default. Inbound traffic is almost all blocked unless specifically allowed and routed as needed - hence your issues

19

Sorry for asking stupid questions.
I am under the conception that if i install an instance of any game server via amp, that amp installs all the neccessary things, i.e. the before mentioned packages of valheim, for me to have an almost plug and play experience. I mean i get that i have to open the ports on my end, but i wonder if there are other things i missed.

I really just set the server up with ubuntu server, threw webmin and amp on and then just started to install the instances. I then opened the ports on the machine and made sure the router was setup too. Am i supposed to do other things that i might have missed?

20

Not stupid questions.

AMP installs a lot of the common dependencies, but can’t cater for every possible scenario that a particular server might throw up.

If it tried to do so, it would be installing heaps of packages on your system that might never be used. No bueno. And it can only do so when you first installed AMP, or are doing a command line apt upgrade.

It can’t do so when you are creating a particular instance since at that point AMP is running as unprivileged user that can’t install system packages.

If you used docker, then that would likely give a few more packages (including those two for Valheim) which would address the issue.

But again, if the docker images had every single possible package that any given server needed, then they would be massive and bloat your system unnecessarily.

AMP isn’t a simple Docker frontend with bespoke images for each separate server. It needs to work without Docker as well. And it has only generalised images that are meant to be common across various servers.

If additional packages are needed, you are normally told that when creating the instance. Valheim is an exception since those packages aren’t required for the server itself to run. The crossplay issue only surfaced later anyway after the template was added.