ich777

But I really don't think that's necessary because newer Kernel versions are supporting that Chip from what I know.

@doguitar & @Marcel40625 looks like that this is an issue with the game itself: Click Anyways, please update the container, I've pushed an update which should make it work again.

Please see here:

I think this is an issue on the Valheim Plus side and that it needs to be updated but that‘s out of my control. You can report that on the Valheim Plus GitHub if not already someone reported that here (I saw that already created an issue about 15 hours ago with the title „Valheim Crashes“).

So evrything is working now for you, of course with a different servern name?

& @doguitar I will look into that ASAP and keep you updated.

Have you also changed the ports as described in the recommended post on top of this thread? So it is a server name issue? Also make sure that you use at least 6 characters for the password...

I really can't help with mods and such since I don't play Mordhaus, or even own it, this was one of the last games that I did on request so I really can't help here. I can only tell you that if you search something you or the paths relative to the paths in the linked page are located in your appdata within the "mordhau" directory But where to put everything I really can't help since I'm not familiar with the game itself.

On what Unraid version are you? Please make sure that you are on the latest Unraid version or post your Diagnostics please. Something really funky is going on on your system... Have you yet tried to restart Unraid?

But you can join from LAN? If that's the case some weird network related issue must be the cause of this. Sounds maybe stupid, but have you already restarted your router/firewall? This is something completely different or do you host on your Windows PC also the dedicated server? Usually if you are opening a session in game where your friends can join, this is done through Steam and their network and so on... What port forwarding have you done in your router?

Wie gesagt, Unraid 6.11 wird dann auf Kernel 5.18 sein auf dem dann diese Option auch enthalten ist aber da du vermutlich auf Unraid 6.10.3 bist welches auf 5.15.3 basiert ist die option noch nicht mal im Kernel drin und du kannst das nicht an schalten. Gedulde dich noch ein wenig 6.11 ist schon am Horizon...

My issue with this is that I don't know your exact network setup and I'm really not a network expert when it comes to something like your setup, sure basic VLANs and such are no issue for me but when it comes to a more complicated setup I really can't help as much as I want too... I will think about this a bit more but I really can't imagine what's preventing the two system to talk to each other...

That is really weird but I really can't help there, I can only thing of a routing issue in your network somewhere since everything is working on many other networks just fine. Did you also set up proper routing tables on Unraid too?

What game are we talking about? If you are talking about Valheim or V-Rising it is almost a similar story because they are both based on the Unity engine. Do you mean visible in terms of visible that it appears on the server list or do you mean that you can connect via your public IP? If you mean that it can take quite a lot of time to show up on the in game server list (should be also the same as you browse it through the Steam Server Browser) than I think the answer is yes because these two mentioned games above are highly played games and the main servers from them seem to be struggling to displaying everything on the server list. However you should be able to connect through your public IP if you can join already through your LAN, if not it is maybe a thing of hair pin NAT that your Router/Firewall doesn't fully support or isn't configured properly (try to connect through your public IP from a different network or ask someone if he can join via direct connect through your public IP).

What are the two subnets? Are you really sure that those are not the Docker subnets that you are trying to connect to? I'm really not sure what is going on but barely nothing is hard coded to my plugins, the exporters should listen to all IPs since I'm mostly using 0.0.0.0

@aRcaNia & @Stolas & @Hokie Saiko & @TimNL81 fix for Valheim is applied, but you first have to update the Docker container and after that restart it so that it moves the directory where it should belong now That's the downside of the automatic update function... For everyone else who experiencing that he starts on a new world on his Valheim server: Stop the container Go to your Backups folder (usually in .../valheim/Backups and open the latest Backup tar.gz file In the tar.gz archive go into the worlds folder and extract the contents to .../valheim/.config/unity3d/IronGate/Valheim/worlds_local and overwrite the existing files in there Start the container again

Try to restart the Docker service once or do a server reboot and see if it fixes the issue.

This is a thing from Jellyfin and can be changed in the menu, if not please create a dedicated issue for that on GitHub if you don't work it out because that's out of my control and should be reported to the developers from Jellyfin itself. This is also a thing that you should report on their GitHub: Click

@Hokie Saiko & @aRcaNia & @TimNL81 I have to look into this and will report back. For all others having issues with Valheim, I will report back when I got a proper solution and the container is updated. Fix applied, update the container in the first place and then restart it.

These are client change notes or am I wrong?

Keep in mind this is a "test" release and I would encourage you to not use it on productive systems because these releases can lead to data loss <- for real... Just saying...

Do this from a Unraid terminal: echo "blacklist i915" > /boot/config/modprobe.d/i915.conf and reboot the Server.

Unraid, hab doch ein Plugin geschrieben dafür... Aber ist noch nicht fertig und momentan hab ich echt schlecht Zeit dafür es weiter zu Entwickeln aber ich tuh mein bestes. Es funktioniert auch noch nicht alles (wegen fehlendem systemd beispielsweise) und bitte vorher Anleitung lesen. Bitte nicht vergessen, ist LXC ohne LXD weil das zu viele Abhängigkeiten hat und mir das Leben nur unnötig schwer machen würde... Sieht bei mir so aus:

Hab jetzt alles in einen LXC container umgezogen und bin restlos zufrieden...

Auslöser dürft auf jeden Fall ein oder zwei USB Sticks sein die du an deine HomeAssistant VM durchgereicht hast.