1 hour ago, NotYetRated said:

Thoughts on where to start looking for issues on my end? I run your Valheim server without issue, but can't get Icarus to allow me to connect. Trying to join locally with server IP:PORT, not working. 

Something seems different form your log, the last line should be something like this:

[2023.08.26-18.48.34:956][344]LogIcarusGameModeSurvival: --------  Server is now empty  --------

 

I attach my log here from a startup after a update and I now tried it and it's just working fine.

 

On what Unraid version are you? Make sure that you are on something recent like 6.12.3 (I'm on 6.12.4-rc19 <- next branch).

 

It should also automatically be listed under local (even if you haven't opened the ports yet: icarus.log

Here is also a screenshot:

1 hour ago, ich777 said:

Something seems different form your log, the last line should be something like this:

[2023.08.26-18.48.34:956][344]LogIcarusGameModeSurvival: --------  Server is now empty  --------

 

I attach my log here from a startup after a update and I now tried it and it's just working fine.

 

On what Unraid version are you? Make sure that you are on something recent like 6.12.3 (I'm on 6.12.4-rc19 <- next branch).

 

It should also automatically be listed under local (even if you haven't opened the ports yet: icarus.log

Here is also a screenshot:

 

Strange. Creating a prospect on my desktop, then transferring the files to the appropriate folder on the Unraid server, I can get it to the same "Server is now empty" log entry, but cannot see the server in my local game browser.

 

I too am on 6.12.4rc19.

48 minutes ago, NotYetRated said:

Strange. Creating a prospect on my desktop, then transferring the files to the appropriate folder on the Unraid server, I can get it to the same "Server is now empty" log entry, but cannot see the server in my local game browser.

Can you maybe try to start over by deleting the container, deleting the directory for Icarus from your appdata and pull a fresh copy from the CA App?

 

Maybe something went wrong at the first start up, which can take quite some time and it has to complete successful otherwise it can cause issues.

3 hours ago, ich777 said:

Can you maybe try to start over by deleting the container, deleting the directory for Icarus from your appdata and pull a fresh copy from the CA App?

 

Maybe something went wrong at the first start up, which can take quite some time and it has to complete successful otherwise it can cause issues.

Ill give that  shot, thanks!

Hi,

First of all, thank you very much for all the work with the Game Server Containers. My friends and I are currently using the Valheim container and it works really well.
Would it be possible to get a dedicated server docker for Life is Feudal:YO?

Kind regards
Atreia

Is there a way to run the satisfactory server with mods? Transferred my desktop pc's mods, but server just bootloops. 

1 hour ago, Atreja said:

Would it be possible to get a dedicated server docker for Life is Feudal:YO

Maybe, but I have stopped creating containers for games that I don't own because giving support for such games if something isn't working is a nightmare and Life is Feudal:YO is one of the games that I don't own.

 

If you however donate it to me I can look into it.
(I can't tell for sure if it's going to work because I have to use WINE since it's only available for Windows only)

51 minutes ago, Duckers said:

Is there a way to run the satisfactory server with mods? Transferred my desktop pc's mods, but server just bootloops. 

I don't know if the same applies to Satisfactory but for most game servers the mods are OS dependent, so to speak if you have a mod for Windows that doesn't mean that it has to work on Linux.

 

Transferring mods across different OS is always a bad idea, you should add them one by one and see which mod is breaking the container since it is possible to run the container with mods (keep in mind, this container is nothing else than if you run Satisfactory on bare metal but the download and start from the game is automated).

 

BTW modding is always up to the user since I can't know every mod, I only provide the basic functionality.

Setting up sons of the forest I keep failing the ports open check in the log. 

I've opened the ports. They show up as open on port checks. But sons will not register them being open. 

 

I changed the port numbers in the container and server config files to ports i know work for another game(the game docker was disabled to avoid conflicts) and I still get the 3 ports show up in the log as closed. 

1 hour ago, ToastedPirate said:

Setting up sons of the forest I keep failing the ports open check in the log. 

Please post your logs.

 

1 hour ago, ToastedPirate said:

I changed the port numbers in the container and server config files to ports i know work for another game(the game docker was disabled to avoid conflicts) and I still get the 3 ports show up in the log as closed. 

I'm also not sure if I'm following this, have you changed the ports?

 

Please also see this post where a user had almost the same issue and I've posted a link to a possible solution:

 

1 hour ago, ich777 said:

Please post your logs.

 

I'm also not sure if I'm following this, have you changed the ports?

 

Please also see this post where a user had almost the same issue and I've posted a link to a possible solution:

 

I tried that fix earlier and it sent an error, but this time it worked. I did something stupid I guess. Thanks!!
 

15 hours ago, ich777 said:

I don't know if the same applies to Satisfactory but for most game servers the mods are OS dependent, so to speak if you have a mod for Windows that doesn't mean that it has to work on Linux.

 

Transferring mods across different OS is always a bad idea, you should add them one by one and see which mod is breaking the container since it is possible to run the container with mods (keep in mind, this container is nothing else than if you run Satisfactory on bare metal but the download and start from the game is automated).

 

BTW modding is always up to the user since I can't know every mod, I only provide the basic functionality.

Gotchu. That cleared it up as it's most likely then OS dependent. I will ask the devs for the 2 main mods i'll be using and ask if they could make one for linux as well

I'm having an issue with the Minecraft Bedrock docker image where it regularly overwrites the allowlist.json file in my appdata folder with a blank one. Minecraft Bedrock migrated from whitelist.json to allowlist.json awhile back and I suspect the docker image is preserving the old one but not the new one. Thanks!

5 hours ago, IBrake4Frogger said:

I'm having an issue with the Minecraft Bedrock docker image where it regularly overwrites the allowlist.json file in my appdata folder with a blank one.

Do you stop the container before editing the file your do you edit the file and then restart the container?

 

5 hours ago, IBrake4Frogger said:

I suspect the docker image is preserving the old one but not the new one. Thanks!

The container does only start the Minecraft Bedrock server and does nothing to the config files or is this only happening after a new release from Minecraft Bedrock is installed?
I make a little change to the update routine, this should preserve the allowlist hopefully.

The update will be available in a few minutes (you have to update the container itself).

So im having one realy wierd problem. As soon as i install the v-rising server my whole server shuts down.

 

Anything i can do to problemshoot this?

1 hour ago, Mr.pink said:

So im having one realy wierd problem. As soon as i install the v-rising server my whole server shuts down.

Can you explain this a bit more in depth?

The Diagnostics from you system would be also helpful since I don't know anything about your system, what power supply do you have,...?

 

Does it instantly shut down when you install the container or does it take some time?

1 minute ago, ich777 said:

Can you explain this a bit more in depth?

The Diagnostics from you system would be also helpful since I don't know anything about your system, what power supply do you have,...?

 

Does it instantly shut down when you install the container or does it take some time?

 

I install the docker as normal. Had it running before without problems.

 

But eathier it restarts the whole machine after extracting the pulled files and i can press done or it takes like 30-40 seconds when it trys to start it. Then i have to start the array and more or less speed stop the docker or it could crash the server again.

 

6 months ago (or something when they released groomlot expansian) i could run 4 servers with that docker without problems.

 

Just for fun i tried multiple different gameservers (valheim, satisfactory, factorio) to see if it did the same but no nothing happened, all dockers ran like butter in the sun without problems.

 

It could take some time or almost instant.

attached the latest diagostic file.

 

mos-diagnostics-20230829-1721.zip

2 hours ago, Mr.pink said:

It could take some time or almost instant.

This is really strange since a container shouldn't be able to crash the host.

 

2 hours ago, Mr.pink said:

But eathier it restarts the whole machine after extracting the pulled files and i can press done or it takes like 30-40 seconds when it trys to start it.

This is a really strange behavior and I've never heard of such an issue before.

 

Do you experience any power spikes or something like that? What power supply are you using, could it be possible that it is the cause?

 

However can you do a memtest? This sound more like a issue that another user had with another container (sorry but I couldn't remember which one it was) but the culprit was a defective RAM stick and it only happened with this specific game server.

This is of course just a vague guess but I've now also tried it and the container is running for almost two hours on my i5-10600

4 minutes ago, ich777 said:

This is really strange since a container shouldn't be able to crash the host.

 

This is a really strange behavior and I've never heard of such an issue before.

 

Do you experience any power spikes or something like that? What power supply are you using, could it be possible that it is the cause?

 

However can you do a memtest? This sound more like a issue that another user had with another container (sorry but I couldn't remember which one it was) but the culprit was a defective RAM stick and it only happened with this specific game server.

This is of course just a vague guess but I've now also tried it and the container is running for almost two hours on my i5-10600

 

 

Nope no power spikes or anything. gonna do a memtest tonight just to see. Otherwise i have no clue what the problem could be.

11 hours ago, ich777 said:

Do you stop the container before editing the file your do you edit the file and then restart the container?

I've mostly been allowing users from within the game or rcon and so it writes out the allowlist.json file. I've then backed up the file so I can restore it when it disappears again. Restoring sometimes fails and that may be because I need to stop the container first -- I'll try that next.

 

11 hours ago, ich777 said:

is this only happening after a new release from Minecraft Bedrock is installed?

Yes, I suspect this is the case but I have not tested it since I have a backup plugin that restarts the containers weekly. On restart it would automatically update.

 

11 hours ago, ich777 said:

I make a little change to the update routine, this should preserve the allowlist hopefully.

The update will be available in a few minutes (you have to update the container itself).

Thanks! I'll give it a try.

1 hour ago, Mr.pink said:

 

 

Nope no power spikes or anything. gonna do a memtest tonight just to see. Otherwise i have no clue what the problem could be.

got a bit further...

 

Now the container loops (server starts and crashes loops it seems) But i get this in the unraid logs.  and that keeps repeating itself. if i stop the container it stops putting this out. @ich777

Quote

Aug 29 21:20:36 MOS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): vetheae5db4: link becomes ready
Aug 29 21:20:57 MOS kernel: docker0: port 1(vetheae5db4) entered disabled state
Aug 29 21:20:57 MOS kernel: vetheaaddb4: renamed from eth0
Aug 29 21:20:57 MOS kernel: docker0: port 1(vetheae5db4) entered disabled state
Aug 29 21:20:57 MOS kernel: device vetheae5db4 left promiscuous mode
Aug 29 21:20:57 MOS kernel: docker0: port 1(vetheae5db4) entered disabled state
Aug 29 21:20:57 MOS kernel: docker0: port 1(veth2ce1934) entered blocking state
Aug 29 21:20:57 MOS kernel: docker0: port 1(veth2ce1934) entered disabled state
Aug 29 21:20:57 MOS kernel: device veth2ce1934 entered promiscuous mode
Aug 29 21:20:57 MOS kernel: docker0: port 1(veth2ce1934) entered blocking state
Aug 29 21:20:57 MOS kernel: docker0: port 1(veth2ce1934) entered forwarding state
Aug 29 21:20:57 MOS kernel: eth0: renamed from veth3e4a4d1
Aug 29 21:20:57 MOS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth2ce1934: link becomes ready
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth2ce1934) entered disabled state
Aug 29 21:21:20 MOS kernel: veth3e4a4d1: renamed from eth0
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth2ce1934) entered disabled state
Aug 29 21:21:20 MOS kernel: device veth2ce1934 left promiscuous mode
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth2ce1934) entered disabled state
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth52fc367) entered blocking state
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth52fc367) entered disabled state
Aug 29 21:21:20 MOS kernel: device veth52fc367 entered promiscuous mode
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth52fc367) entered blocking state
Aug 29 21:21:20 MOS kernel: docker0: port 1(veth52fc367) entered forwarding state
Aug 29 21:21:20 MOS kernel: eth0: renamed from veth72f3cdf
Aug 29 21:21:20 MOS kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth52fc367: link becomes ready

 

On 8/6/2023 at 11:07 PM, capitanforketta said:

 

can you help me to use my key for assetto corsa server?

thank you so much

 

Hello, sorry for the late response.

 

If i can remember, you need put the license file into the server directory.

Stop/start or reboot.

Edited August 29, 20232 yr by Vitor Ventura

36 minutes ago, Mr.pink said:

But i get this in the unraid logs.  and that keeps repeating itself. if i stop the container it stops putting this out.

This is the default messag that a container produces if you start and stop it.

 

37 minutes ago, Mr.pink said:

Now the container loops

A bit more detail please. Stop the container and post the full log please.

55 minutes ago, ich777 said:

This is the default messag that a container produces if you start and stop it.

 

A bit more detail please. Stop the container and post the full log please.

 

The log from diagnostics is attached

mos-diagnostics-20230829-1721.zip

7 hours ago, Mr.pink said:

The log from diagnostics is attached

Sorry, I don‘t meant the syslog since this is the default message when a container stops/starts, I meant the log from the container.