ich777

Please don't tell people wrong things, if you read the messages again you would know that it initializes just fine: It found steamclient.so (which is needed for the API) It failed because it tried to quick to access the API And the last line says that it initialized successful So to speak it is working, again please don't tell people wrong things, this messages appear on almost every game server, not only in my containers also on bare metal. Do you have a log? The API is simply not the cause of the issue in your case, have you yet tried to add the server in the Steam Server Browser (in Steam View -> Server Browser -> Favorites -> Add) with your LAN IP. I would first recommend getting it to work in your local network and after that you can try to reach it from outside and see it in the server list.

In which list? The in game server list? Have you yet tried to add it to the Steam Server Browser as a Favorite (in Steam View -> Server Browser -> Favorites -> Add) with your LAN IP? I haven't played RUST in a long time but I will try it today evening and report back if the new ports are working. Nothing to worry about, this is just a warning and as you can see, the first line says that it found steamclient.so, after that it fails because it tried it too quick and at the end it says that it is initialized. This is a common message and almost every game server displays it in this exact order when starting it, even on bare metal.

Why not? They even have it on their homepage listed and mention that it is complicated but doable... Sorry if lancache isn't working correctly I can't help since I don't maintain the Lancache or Lancache-DNS containers, you can also go to their Discord which is listed here (I run a completely different setup over here, I run a LXC container where Unbound, AdGuard and LANCache Monolithic are installed and handle all DNS requests).

Sure thing, as mentioned in the template here: https://github.com/tpill90/battlenet-lancache-prefill#detailed-command-usage (or you can scroll a bit up to this bit: https://github.com/tpill90/battlenet-lancache-prefill#selecting-what-to-prefill) Or you can open up a container console and run the following commands: Type in 'su $USER' (case sensitive!) and press ENTER Type in 'cd ${DATA_DIR}/BattleNetPrefill' and press ENTER Type in './BattleNetPrefill list-products' and press ENTER Then you should see something like that: Yes, every time the prefill run it will check for updates, so to speak patches and prefill them.

So it seems to me that lancache is not working, I would recommend that you head over to the Lancache GitHub and create an Issue there: Click I can only give support for Lancache-Prefill.

Form? You mean the Docker template correct? I would maybe recommend that you start over by deleting the container, deleting the folder for the container that was created in your appdata directory and pull a fresh copy from the CA App. Please head over to @Spectral Force's Discord for help with 7DtD, he helps me out with that: https://discord.gg/VwwYA5h Do you have any Ad-Blocking software or something similar on your network? Don't add your Steam Credentials, they are hidden for a reason in the template, the credentials are only needed if they are marked with a red asterisk (*). Please post screenshots from your Docker template.

Are you sure that the container supports HW transcoding? I don't think that non of the Nextcloud containers in the CA App support HW transcoding.

Maybe someone else can help, I'm really not that familiar with PhotoSync and authentik... However if you find the solution please let me know.

Most of the times something with glibc and the compiler in general prevents the containers from running. Are you also sure that you've put in the correct UID and GID? Have you yet tried another container which not uses WINE? Something like CS:Source? Can you give me the error message about that please, maybe post the full log so that I can see what's working and what is not working. docker container logs CONTAINERNAME > /path/to/output/vrising.log Will give you the full container log and write it to the file, of course change CONTAINERNAME to the exact container name from V-Rising (case-sensitive).

Can you explain a bit more in detail what this is? Can't you just install it and put the files in the appropriate folders if it's a mod pack, or is it a dedicated modded version from the game?

Thank you for the report, I've pushed an update to the container itself so that it supports the new ports too, please update the container first after that make sure that you have the following port mappings in your container: Protocol HOST Port CONTAINER Port UDP 28015 <-> 28015 UDP 28016 <-> 28016 TCP 28017 <-> 28017 TCP 28018 <-> 28018 I've also update the template now too, but existing installations have to create the port mappings on their own.

This has nothing to do with the container, you have to install Squids Fix from the CA App:

A user had last week a similar question, please read my answer here:

Can't find any information on dedicated servers for this game.

Sollte funktionieren wenn die Intel eine 10th Gen CPU ist, zumindest in der Theorie und abhängig davon wie der Hersteller des Boards das alles implementiert hat.

GVT-g funktioniert auf 11th Gen CPUs nicht, normalerweise unabhängig vom Chipsatz.

Not really, is your Distribution up to date? I've got some issues in the past with users who where using older version from Unraid because there where some libraries form the host out of date. Anyways here is a log from a successful start from the container (looks a bit convoluted but it's up and running) : vrising.log

Because the container uses the basic listen and RCON port as it is specified in the template. You should be able to do it like that but I would rather recommend doing it in the template like: But please keep in mind that you have to delete the old port forwarding in the template and create new ones with the appropriate ports set with container and host port to the same as you've specified. Ark is a really convoluted game in terms of the in game server list, I would recommend that you first try to add it in the Steam Server Browser in your Favorites and see if it shows up properly.

I think the game isn‘t released yet or am I wrong? AFAIK the developers plan to release a dedicated server but I have to buy the game first and look into how things are working an also if they release a native Linux dedicated server version.

On what Unraid version are you? Can you please post a screenshot from your template(s).

Please post your full Diagnostics.

Thank you for the heads up but there should be no issue because the images are already based on Debian 11 so there should be no incompatibility issue.

A little bit more context would be nice. What container are you using? The config would be also helpful. What do you want to do with the container? Your error is right here: LXC on Unraid is built without AppArmor because Unraid uses SELinux.

Firewire drivers are now included in Unraid itself. I really don't understand how that all works but wouldn't this be somehow also be controlled by SageTV and you should look up the documentation on SageTV? Firewire is only the bus and with Firewire alone you can't control anything, you need some kind of interfacing application that connects to the Box over Firewire. Hope that makes sense to you. EDIT: Maybe these posts will help: https://forums.sagetv.com/forums/showthread.php?t=37086 https://forums.sagetv.com/forums/showthread.php?t=40568 https://forums.sagetv.com/forums/showthread.php?t=38466 https://forums.sagetv.com/forums/showthread.php?t=35718

But from what I see in the disagnostics that you've sent over after you've changed it it is not applied: Jan 26 19:19:34 CD1GIT-Unraid kernel: Command line: BOOT_IMAGE=/bzimage pcie_acs_override=downstream initrd=/bzroot Otherwise it would show up in the above posted line. Did you reboot after you've applied that setting? Is "Unraid OS" your default boot method? Please run: lxc-checkconfig From a Unraid Terminal and post the full output.