ich777

Thanks for joining in here Frank! I think you don't know this but on Unraid it would be better to pass this over with the syslinux.conf like: it87.ignore_resource_conflict=1 or you could also do this with a file in /boot/config/modprobe.d/i87.conf with the content: options it87 ignore_resource_conflict=1 and reboot afterwards regardless of which method you choose.

These are messages from WINE. What is the exact issue? Is the server not running? I could however hide the messages but I decided to not do that because such messages should be visible. Usually these are not real errors and the server is just running fine. I don't understand what you mean with that, the messages won't go away and are usually nothing to worry about.

I think this is then an issue with your mobile client or better speaking with your WebDAV server or am I wrong? You host your data on WebDAV, I assume you use Nextcloud? I have no issue syncing my Vault between my container, Android, Windows, Linux and iOS.

Nein, das funktioniert leider nicht.

For Terraria you have to set the version in the template manually and it will download it after the next start: Don‘t forget that my containers work differently and they pull the updates on every start/restart but since Terraria has no real API where I can pull the latest version you have to set it manually.

Yes. Yes, but there is a bug in the newest test build in it. Please wait a bit longer.

I have to be completely honest, I'm a little frustrated because you are double posting (Private Message and here in the support thread). I won't answer any quicker... I've already answered via PM but I will copy paste it here and leave the first paragraph out because you've don't mentioned the Unraid version in your PM: What do you mean with this? If you upgrade the Unraid version or on reboots? If you don't want to upgrade it on reboots then simply change the driver version to the version that you want to stay on instead of selecting latest. I can't/wont change the behavior for Unraid upgrades since I don't know how long Nvidia will support the legacy 470.xx drivers, if they want to they can support tomorrow (or even today). That's the reason why there is no legacy button in the driver plugin in terms of the version selection. I can't compile these drivers for newer Unraid versions because they won't compile against newer Kernel versions which Unraid is on, if you want that old drivers you have to stick with that old Unraid versions. Please remember this is the proprietary driver and not the open source one... I also won't compile the open source Kernel module because this would basically break the driver for every card pre Ampere so to speak this would also break compatibility with your system because you are having a Turing card. BTW, are you sure that driver version 470.141.03 is also not working because these are the "newer" legacy drivers which actually support newer Kernel versions: Click

You inject a private Docker registry to /etc/docker/daemon.json from your go file. Please remove that from your go file and reboot your server. After you‘ve rebooted you will see that your daemon.json has the changes for the nvidia runtime in it. If you want to keep that private Docker registry, you have to also customize your injection into the file that it includes this changes for the nvidia runtime. From what I saw it also looks very suspicious that you have: {undefined at the start, are you sure that this is correct?

Can you send me your Diagnostics? This should be also fixed with newer build from Unraid. Stick to 6.10.3 until a new release is published.

RCON was never made to be sent over the Internet, it is always up to thenuser to secure it through SSH ar somehong like that. Have you forwarded all the ports correctly in your router? I really can‘t help wih this because it‘s a mod that I‘m really not familiar with.

I've never used them on a dedicated server, do you made sure that you are the admin? I'm pretty certain that those sever use mods to accomplish this since you can't use cheats on a dedicated server AFAIK. However a quick Google search gave me "Quality of life" and "SkToolbox" mod, pretty sure that those servers use these mods. Shouldn't be to hard to install on the container itself, but remember modding is always up to the user...

Maybe the webserver can't talk to your container. BTW Please don't route RCON traffic over the internet because it is unencrypted plain text!!!

Please double check if you've set the ports correctly, created the ports correctly and also check the password again. Maybe try to connect with a RCON client to try if its even working...

Sorry I'm not really into ARK, can you maybe provide some information on what you are doing there, I even don't know what Amunet is. Usually modding is up to the user, I provide only the basic container because I can't give support for every game server or even mod because I can't know them all.

Ah, now I get it... Leave the REMOTE_DIR empty and create a new Path like that by clicking : After you did that click Add and Apply and you should find the folder inside the container in /mnt/remoteshare The REMOTE_DIR is only in the template for use with SFTP/FTP servers, you can also delete REMOTE_USER and REMOTE_PWD Hope that helps.

Sure thing, on bare metal that is enough, but since the game server is running in a container you have to add a port mapping too. Click on the container icon Click on Edit Click on From the drop-down select "Port" at container port and host port enter the port that you've specified for RCON in the config something like: Click Add Click Apply Now your container should be reachable on that port via RCON.

I almost completely forgot that I have a card that is based on the same chipset... 🤦‍♂️ The issue is now solved but you have to wait until a new RC release from Unraid is released if you want to upgrade since there where some changes needed in the base OS to make it again work.

Oh sorry, forgot how to do that: Go to https://unraid.net/download On the bottom download the archive for 6.10.3 Replace all bz* files and the changes.txt from the archive with the ones on your USB Boot Device (but don't replace anything else!!!) Reboot I will get back to you if I know more and have a new build to test if that's okay for you.

Have you mapped the share in the container template too (also please don't forget to select R/W Slave in the template)? I recommend to mount these shares separately. In the container you have the folder /mnt/sourcepath where your Unraid root directory is mounted in but that is only for reading files since it's read only by default.

I would recommend that you downgrade to 6.10.3 so that your card is back in a working state.

Something seems wrong with some symbols in the module, have to look into this tomorrow, getting pretty late here... Will report back when I know more.

Please upgrade to RC5 again and it should now work again, thank you for the report!

My container was only designed to backup data to Mega or from Mega to a share.

Sorry, had to be more clear I think... What was the last Unraid version where it was working?

I think you are talking about the other container which is running Firefox or am I wrong? My container is not designed to work in conjunction with another container. You should have such a little arrow on the left side: If you expand it and click on the clipboard you should get a window like this where you can paste something that is handed over to the app that is running inside the container: