Hello,

 

I wanted to use your openTTD container but I am finding it is missing some libraries and crashes on run.
I've opened a github issue with the problem log output and the necessary fix (adding two libraries to the apt-get install line in the Dockerfile).
I'd submit a PR directly but it does not appear I can. Do you still take fixes for your existing containers or should users fork it?

Thank you for your work and even thinking of a game like openTTD!

Edited April 23, 20242 yr by owlman
parenthesis

4 hours ago, owlman said:

I wanted to use your openTTD container but I am finding it is missing some libraries and crashes on run.

Thank you for the report!

 

4 hours ago, owlman said:

I'd submit a PR directly but it does not appear I can.

I also don't see a PR, however I changed the library libglib2.0-dev to libglib2.0-0 since the development package is not needed.

 

4 hours ago, owlman said:

Do you still take fixes for your existing containers or should users fork it?

Sure, I still maintain these container.

Just because I don't accept any new requests for game server doesn't mean that I dropped support for existing containers.

 

The container is already updated and is working again.

Thanks again for the report!

16 hours ago, Maitresinh said:

Maybe you can see the server (romero-popollo) ?

I have to try but this will take some time since I'm really busy currently...

 

16 hours ago, Maitresinh said:

Could it be a probleme with the client ?

I' ve noticied that the "Ip" file is not showing up.

Have you yet tried to reinstall your game on your local PC?

 will install the version 41.76.16 and check. thanks for your time and patience.

2 minutes ago, Maitresinh said:

 will install the version 41.76.16 and check. thanks for your time and patience.

Do you install a specific version from the game instead of the latest available?

 

Please note that the container usually pulls the latest version and older versions from the game had a completely different requirement in ports.

7 hours ago, ich777 said:

Thank you for the report!

 

I also don't see a PR, however I changed the library libglib2.0-dev to libglib2.0-0 since the development package is not needed.

 

Sure, I still maintain these container.

Just because I don't accept any new requests for game server doesn't mean that I dropped support for existing containers.

 

The container is already updated and is working again.

Thanks again for the report!

Works great, thank you so much!
And the missing PR was my mistake, got my auth wrong and didn't read right. 🤦‍♂️

Thanks for the extremely prompt update

This has probably been answered 100 times but I was unable to see the answer so I'm sorry in advance.

 

My ark survival server running through an unraid docker began having issues after adding variables into the "Game Parameters:"

 

I had removed the ones I added then removed all of them, double checked for spaces anywhere, but have gotten the following error:

/opt/scripts/start-server.sh: line 72:    64 Segmentation fault      ./ShooterGameServer ${MAP}?listen?SessionName=${SERVER_NAME}?ServerPassword=${SRV_PWD}?ServerAdminPassword=${SRV_ADMIN_PWD}${GAME_PARAMS} ${GAME_PARAMS_EXTRA}

 

I'm not sure what me adding those two variables done to the server but would like assistance if there is any and to save my saves at least.

33 minutes ago, DisplayFusion said:

I'm not sure what me adding those two variables done to the server but would like assistance if there is any and to save my saves at least.

Have you yet tried to set up a second instance and see if that works, I know it sounds kind of silly but please try and see if that solves your issue.

 

You just have to stop your first container, give the new container another name and change the path to the game files.

 

I only see those kind of issues on non supported CPUs but I assume it was working before.

It could also be the case that your game files got corrupt but I haven't seen that only once for a Ark server.

Minecraft just updated to 1.20.5 this morning, and now my server isn't booting. Looking at the log I'm seeing the following error:

 

Error: LinkageError occurred while loading main class net.minecraft.bundler.Main
        java.lang.UnsupportedClassVersionError: net/minecraft/bundler/Main has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0

 

Any idea how would I go about updating the JRE to get past this?

20 minutes ago, ich777 said:

Have you yet tried to set up a second instance and see if that works, I know it sounds kind of silly but please try and see if that solves your issue.

 

You just have to stop your first container, give the new container another name and change the path to the game files.

 

I only see those kind of issues on non supported CPUs but I assume it was working before.

It could also be the case that your game files got corrupt but I haven't seen that only once for a Ark server.

Created a second instance, didn't work, BUT I did change the map from "TheIsland" to "Genesis" on one of the containers and works fine.

 

I also moved the saves from the server files which works and let it create a fresh save which... unfortunately works.

 

So it's looking like the saves for whatever reason is now corrupted after me adding two variables regardless of what variables I enter and which backup of the save I put into the servers saves, even ones days before I changed anything.

 

Am I out of luck or is there a workaround?

10 hours ago, estuine said:

Minecraft just updated to 1.20.5 this morning, and now my server isn't booting. Looking at the log I'm seeing the following error:

Thank you for the report!

 

Please update the container itself, after that edit the template, at the bottom click on Show more settings... and at Runtime Name enter "jre21" (without quotes) like:

 

After that the container will start, download the new JRE and maybe restart one more time.

10 hours ago, DisplayFusion said:

So it's looking like the saves for whatever reason is now corrupted after me adding two variables regardless of what variables I enter and which backup of the save I put into the servers saves, even ones days before I changed anything.

It can be possible if the container was just starting and you changed right a value while it was starting and couldn't save successfully that it got corrupt but that is really a edge case that I never saw.

 

As said before I have seen that only one time that a save game became corrupt on a Ark server.

 

10 hours ago, DisplayFusion said:

Am I out of luck or is there a workaround?

You can try to move the savegame to a Windows machine and import it there and see if it is working.

Do you maybe have a backup from your appdata where an "old" save is included?

hi i dont know what i do wrong

 

i install the pix ark server and get this

 

0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:err:virtual:virtual_map_section mapping 0x14ac2caf0000 11000 0 failed
0024:fixme:imm:ImeSetActiveContext (0000000000010070, 1): stub
0024:fixme:imm:ImmReleaseContext (000000000002006E, 0000000000010070): stub

 

some one now what i do wron?

Is there a way to make ASA visible to the game without making opening a port to the outside world?

7 hours ago, AlaskaBvR said:

Is there a way to make ASA visible to the game without making opening a port to the outside world?

I'm not 100% sure because this is a game specific question but couldn't you connect through the in game console or via filtering LAN games only or simply by connecting through your servers LAN IP?

First of all, thank you for the awesome docker containers!

 

How would I best add these variables, so that I can install the public test of Ashlands?

 

I tried adding the variables like in the attached image, but no luck.

 

Edit:

Solution: put "-beta public-test -betapassword yesimadebackups" (without quotes) in the GAME_ID field after the numbers.

Also added the environment variable PUBLIC_TEST=true, but don't know if that is necessary.

 

@ich777

 

 

Edited April 27, 20242 yr by DogeKitteh007
Added image of attempt to add variables

On 4/24/2024 at 6:22 PM, jearone said:

i install the pix ark server and get this

Sorry, I completely overlooked your post...

 

I tried it now and it seems to have some kind of issue now, sadly enough I made this game on request and I don't own the game so I really can't test what's wrong...

 

Sorry to have bad news but I'll deprecate the container since it's really hard to troubleshoot for me without owning the game.

I'm having an issue with the Ark Survival Ascended docker.  I wanted to test some setting changes in the game, so I created a second container with the previously installed docker.  I deleted and changed the port for the new container from 7777 to 7779. 

 

If both dockers are running, both show up in the game's server select.  They show their unique names and day count.  It doesn't matter which one I select, I end up on the first server.  Inside the game, it shows the first server's name, even if I joined from the second server in the server select.

 

If the first server's docker is running, the second server shows up in the list, but I am unable to connect.  Is there a hidden port setting somewhere that I am missing?

 

 

 

 

I've not had this issue with Ark Survival Evolved in the past, but there seems to be fewer port options in the ASA docker?

 

1 hour ago, Perdan said:

If the first server's docker is running, the second server shows up in the list, but I am unable to connect.  Is there a hidden port setting somewhere that I am missing?

That sounds like a some kind of misconfiguration.

 

1 hour ago, Perdan said:

Something seems very wrong here, you usually choose a source port and then forward that port to the destination or at least a port range...

 

1 hour ago, Perdan said:

I've not had this issue with Ark Survival Evolved in the past, but there seems to be fewer port options in the ASA docker?

Yes, because this dedicated server works differently and you can specify the port here:

40 minutes ago, ich777 said:

That sounds like a some kind of misconfiguration.

 

Something seems very wrong here, you usually choose a source port and then forward that port to the destination or at least a port range...

 

It looks like this in a different view:

 

40 minutes ago, ich777 said:

Yes, because this dedicated server works differently and you can specify the port here:

In the default setup, the UDP port and that port are the same.  When I created the 2nd server, I updated that value to 7779 and deleted the UDP port, created a new Port setting as 7779.  Still end up on the same server somehow.

I saw a post where someone said they manually added the Port=7779 in their gameusersettings file, I tried that as well without success.

 

16 minutes ago, Perdan said:

It looks like this in a different view:

But why do you specify such a big port range? This is not necessary... You only need one port for one server so to speak 7777 for your first server and 7779 for your second one.

 

Are you also really sure that you want to expose the port on both WAN connections? This is maybe also an issues since you are advertising the dedicated server on two different public IPs.

Are you also really sure that you are connecting to the correct server? Do you use two different server names?

If this is a cluster I can't help much because this is a pretty complicated setup that I'm not familiar with.

It could also be possible that the Team behind Ark only allows one server for one IP (this was the case initially).

1 hour ago, ich777 said:

But why do you specify such a big port range? This is not necessary... You only need one port for one server so to speak 7777 for your first server and 7779 for your second one.

 

Are you also really sure that you want to expose the port on both WAN connections? This is maybe also an issues since you are advertising the dedicated server on two different public IPs.

Are you also really sure that you are connecting to the correct server? Do you use two different server names?

If this is a cluster I can't help much because this is a pretty complicated setup that I'm not familiar with.

It could also be possible that the Team behind Ark only allows one server for one IP (this was the case initially).

 

Basically just reused the same ports I used to use for Ark Survival Evolved where I had them running as a cluster.  So there were, 8 servers?  It was many.  I have changed to different ranges for the second server, but it keeps kicking over to the first server.  Even if they are different maps.

 

WAN2 is not active.  Only 1 public IP is available.

 

 

These are the 2 servers.  The Island server is the 2nd server at this point.  If I connect to that one, I end up on the ScorchedEarth server.  ScorchedEarth goes to ScorchedEarth.

 

Island Server

 

Scorched Earth Server

I did redownload the docker and installed it a second time, instead of creating it from a template.  That did not work either.

 

I'm not trying to make these cluster.  Just wanted to test some new settings on a different instance of the server.  I was curious about a hidden port setting somewhere, because the 2nd server (the 7779 one) is never really there.  It only connects to the first server when the first server is running.  If I turn off server 1, server 2 shows up in the server list, but it doesn't connect.  It is behaving like the docker didn't assign the port correctly?  

 

 

for testing purposes, I changed the port forwarding rules.  Connecting to the Island server on 7779 still put me on the Scorched Earth server on 7777.

Edited April 27, 20242 yr by Perdan
picture

36 minutes ago, Perdan said:

for testing purposes, I changed the port forwarding rules.  Connecting to the Island server on 7779 still put me on the Scorched Earth server on 7777.

Ah I completely forget about that, please look at that post:

 

 

Seems like something is broken, stop the container, edit the file and put the port in the mentioned file.

57 minutes ago, ich777 said:

Ah I completely forget about that, please look at that post:

 

 

Seems like something is broken, stop the container, edit the file and put the port in the mentioned file.

 

Gave it a try, no luck.

 

I basically tried to create an ASA server on any port other than 7777 and was unable to.  I'll give it a try another day.

 

Appreciate the advice and all that you do!

Hi, loving the Sven Coop server I've got running using this but rcon seems to be straight up refusing to work. I've set rcon_password in svencoop/svencoop/servers/server.cfg but when I log into the server (with the sv_password which I also set there) and try to use rcon after setting the same rcon_password CVAR in the source console, I get "Bad rcon_password. No password set for this server.". Can anyone help?

 

 

Also, unrelated, playing any Half-Life maps seems to be broken for me as the NPCs don't want to cooperate with players. For instance Barney won't let you out of the tram at the beginning of the game, or through the door once you have your HEV suit. Is there something I'm doing wrong?