CoZ

Nope. Once I finally got it up and running (by changing the previous password in the container to something else) I left it alone. lol

So, the only way to get it from crashing constantly was to change the server's password. Strange. Seems to be working now. Just started up my Valheim docker that never had any issue previously. I am not using any mods at all. It's in some sort of boot loop. Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '896660' already up to date. ---Prepare Server--- ---Server ready--- ---Starting Backup daemon--- ---Update check deprecated!--- ---Start Server--- ---Ensuring UID: 99 matches user--- usermod: no changes ---Ensuring GID: 100 matches user--- usermod: no changes ---Setting umask to 000--- ---Checking for optional scripts--- ---No optional script found, continuing--- ---Taking ownership of data...--- ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/serverfiles/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1679680174 -- type 'quit' to exit -- Loading Steam API...OK Just continues to do this over and over.

Oh? I was told never to ever update anything "inside" the container - only to update the container itself. I was making sure my mouse icon didn't come anywhere near the "Update Now" button on the GUI lol

What are you using to backup? It looks like, from the screenshot, you are using some backup function from within Organizr? I didn't know it had one until now. I just use CA Appdata Backup / Restore v3 and backup all my dockers and their data. Easier / simpler, FYI

I'm hoping the support for this isn't dead. My Organizr keeps bugging me to update it for a while now. I guess there was a new version released some time ago but the docker hasn't been updated to reflect it.

I'm an idiot. lol

Did you get an answer on this because it's happening to me as well. According to some dedicated "pay server" places it started happening after they instituted the "cross-platform play"—so Xbox etc can play with PC players. There is some line in the .bat file of the server that they are deleting. However, they don't say which .bat file it is to disable the cross-platform play, and it fixes the disconnect issue(s).

I went back to page 47, and I see no mention of this—possibly because everyone else is smarter than I am? I've removed the old, installed the new one and went to verify all the settings in the plugin. I'm greeted with this message right on top in bold red letters: So, the previous version I was backing up to /mnt/user/CommunityApplicationsAppdataBackup without one single issue. Two part question (A) why the change? (B) where in the heck am I supposed to back up the appdata to now? Thanks.

Figured it out: You can install it client-side as long as your listed as the admin on the dedicated. You need to install two mods on your local machine: Server Dev-Commands BepInExPack Start Valheim "modded" log into your dedicated server as normal and you can now run all the devcommands to your hearts content.

Sort of off-topic but hopefully someone here knows the answer; is there anyway to run "devcommands" on the dedicated server for Valheim? The normal "kick / ban" etc... work fine if you're listed in the admin.txt file. Just can't figure out how to get access to the (so-called) cheats like you can on a solo server. I think it's possible because some paid-for-rental-Valheim servers have access to it. Thanks, in advance.

Just in case there was any kind of miscommunication, I am NOT blaming you for the world wipeout. I hope you didn't take it that way. I know it was the developers. Furthermore, I didn't know you could configure the backups. Your container has been so rock solid since I installed it, I just kind of "fired and forgot" about looking into anything of that nature.

Well that answers my question when I logged in after a long long time only to find myself back at the spawn point. lol All the other players on my server are screaming bloody murder about it though. I don't care - it's like a fresh start as far as I see it. The automatic server backups only go back a day, so there isn't even a point in trying to restore one of those because it would be a blank world as well. @ich777 How would I go about loading up a "custom world"? Such as one of the ones listed at https://www.reddit.com/r/Valheim_Seeds/

Replying to this for posterity’s sake. The issue has now been resolved. It was, indeed the HDHomeRun Docker causing the issue. It took over port80 when the author of said docker updated it due to Silicon Dust releasing a GUI for the DVR hardware. Unforseen consequence he has stated on GitHub after I opened an issue. In order to access the webgui since the docker took over port 80 the following commands were used: nano -w /boot/config/ident.cfg then looking for the PORT line entry and changing it to a random number and saving the file. /etc/rc.d/rc.nginx restart Then typing in the IP:Newly Assigned Port of the UnRaid server into Edge / Firefox. Going into the Docker tab, stopping the offending Docker and then unchecking "autostart" Reverse the commands above, changing the PORT line entry back to the default of 80 and rebooting the server allowed access once again.

Not sure if this is the correct section for this - so I apologize in advance if it is not. I had a power outage the other day that was long enough to have my UPS initiate a graceful shutdown of my tower and router and modem. The system has been rock solid for years - until this recent power outage. I can no longer access the WebGUI. At first, I thought it was a docker Hdhrdvr causing this issue as it and only two others were in Host mode (Plex and Home Assistant). The reason why I thought it was that docker was due to the fact that every time I tried to access my UnRaid dashboard, the HDHomeRun DVR configuration page would appear instead of the WebGUI. All of my other dockers I can connect to fine <IP:Port> and even the dockers that use VNC show up without issue. I'm able to SSH/PuTTy into the terminal without issue as well. I've run nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful then nginx -s reload: nginx: [error] invalid PID number "" in "/var/run/nginx.pid" I also tried: nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:15 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:16 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:16 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:17 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] bind() to unix:/var/run/nginx.socket failed (98: Address already in use) Message from syslogd@CozsNAS at Jul 5 13:24:17 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: bind() to unix:/var/run/nginx.socket failed (98: Address already in use) nginx: [emerg] still could not bind() Message from syslogd@CozsNAS at Jul 5 13:24:18 ... nginx: 2022/07/05 13:24:15 [emerg] 22438#22438: still could not bind() running netstat -nalp | grep -i 'nginx: master' returned nothing what-so-ever Then trying: netstat -nalp | grep -E 'tcp\s.*(:80|:443).*LISTEN\s' tcp 0 0 0.0.0.0:8091 0.0.0.0:* LISTEN 22673/docker-proxy tcp 0 0 0.0.0.0:8010 0.0.0.0:* LISTEN 14385/docker-proxy tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 13325/docker-proxy tcp 0 0 0.0.0.0:8086 0.0.0.0:* LISTEN 13733/docker-proxy tcp 0 0 0.0.0.0:8089 0.0.0.0:* LISTEN 17567/docker-proxy tcp 0 0 0.0.0.0:8090 0.0.0.0:* LISTEN 13311/docker-proxy I've pinged TOWERNAME from my WindowsPC and it resolves with the static assigned IP address I managed to figure out how to disable the hdrhomerun docker from auto starting and rebooting the tower. Since disabling the hdhomerun docker and rebooting the server and typing in nginx nothing happens. Entering nginx -s reload no errors show up either. Entering in docker network inspect host: "Name": "host", "Id": "937fbdeca1b4fcaf5d1930f1fbbc740461b25c5699070a79cfc49b6755722d24", "Created": "2020-12-09T11:07:08.920604571-05:00", "Scope": "local", "Driver": "host", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": null, "Config": [] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "79c3c4cbb2fa30b3a9bec0a621e56e2f51032c120096c115bdead6aa7a881c25": { "Name": "home-assistant", "EndpointID": "01d6247f536f7cfa0a70cb2314197ec344038e9e975f19c3f862946717ebf5b f", "MacAddress": "", "IPv4Address": "", "IPv6Address": "" }, "d236e30221155a37809b821e4dfb64aa37ced3ee1834a6f950ffd9940ed747c3": { "Name": "PlexMediaServer", "EndpointID": "1ceb127b22c6a92f8975b57f9695382d222b383e8cd472290f38179a764d11c 4", "MacAddress": "", "IPv4Address": "", "IPv6Address": "" } }, "Options": {}, "Labels": {} shows that the HDHomeRun docker is no longer starting on reboot. I am still unable to access the GUI. Looking at the "MyServers" plugin on the forums, it reports that my Tower is online. Trying to access it from the hyperlink on that webpage also just simply timesout. I've exhausted everyone's knowledge and my own trying to figure out what could possibly be wrong now. Some folks on /r/UnRaid were helping but they have since gone silent - I guess they have run out of ideas as to what to try? So now I turn to you fine folk. If it makes any difference I am running an Ubiquiti UDM router (UniFi OS1.12.22 / Network7.1.66) in case the power outage and subsequent reboot of everything might have an effect on something, somewhere. I've also power cycled the cable modem and rebooted the router a few times as a just in case type of thing. I really could use some help here. Thank you, in advance.

So I went and installed this and really didn't like it's functionality that much and I also don't really mess with changing my pre-rolls all that often. I removed the docker and the appdata folder. However, for some reason now none of my pre-rolls will play on Plex. I looked at the settings in Plex itself and everything seems to be as it should and was but, for some reason, none of the pre-rolls are playing anymore. Anyone have any advice? So my paths for my prerolls were almost identical to what this Docker changes the paths too. I had to go back in and double check and change the paths. Got my prerolls back!

I've got an error for the first time in a long time! Error writing trailer of /tmp/unmanic/unmanic_file_conversion-1641179454.3315327/Yellowstone - S04E10 - Grass on the Streets and Weeds on the Rooftops-1641179454.331512-WORKING-2.mkv: No space left on device I've moved the file in question to different drives (SSD / Mechanical) and still the same error returns on this file. Not sure why this has come up as I've encoded 45GB+ Remuxes before without issue.

Just came here to say thanks to @ich777 once again. I've been running your Valheim docker for and happened to see your name attached to some game called Xonotic in Community Apps. Having never heard of it, I went and took a look. Downloaded it and running your container now. Had it not been for your reputation and immediately recognizable username; I might have never heard of this Quake port/clone. Thank you, Sir.

Fixed! No more "bootloop" and I was able to join on my own LAN. Whatever you did - thanks.

Plain 'ole vanilla Valheim

Hey @ich777, you just pushed an update out to the Valheim docker. I applied the update and was unable to connect. Checking the logs, it seems to be stuck in some sort of "boot loop". EDIT: Seems to be everyone's server having issues. No servers are coming up in the server browser at all, much less mine.

So strange things are happening now; the Docker is now encoding files that it has previously encoded. I have two TV shows in the watch folder and even though they have already been encoded, the app is encoding them again to HEVC. This is quite puzzling. Ok, I am an idiot. I had both plugins installed and running: Video Encoder H264 - h264_nvenc (NVIDIA GPU) Video Encoder H265/HEVC - hevc_nvenc (NVIDIA GPU) This is not the containers fault but, my own. Initially upon configuring everything I was in such a rush to get it back up and running I wasn't paying attention and just installed everything with NVIDIA GPU in it. So it seems as though I put the container into a vicious cycle, converting the same files to x264 and then x265. This would also explain why my RAM filled to capacity yesterday and my Dual Xeons spiked to 100% on all cores. I am leaving this post up for posterity in case anyone else has this issue. Check the plugins! lol

Everything is a Plugin now. You're like Oprah now; "You get a plugin — you get a plugin — you get a plugin!" I am actually liking it the more I mess with it. At first, I thought "why have all the functionality taken out by default" but now I realize why you've gone that route; much easier to customize, much easier to nail down errors. Great Job on this Sir. I thought this container was a must-have installation for any Unraid build but now, this certifies it!

That's the first place I went too (well after installing all the HEVC plugins) and it's just blank. I'll re-watch the video to see what I missed. I skimmed through it to get the container up and running again and that was priority 1.

So THIS is why none of my files were being automatically compressed — there was a major update and everything has to be reconfigured. LoL! This shows you how bulletproof this docker was. I set it up once and never again had to look at it. Thanks for the video @Josh.5 - that helped. It did however take a few start / stop / restart of my docker container before it actually started to do anything. Not sure why that happened? Strangely that old container seemed to have skipped some files(?) because now I've got an entire season of a watched series undergoing a conversion. Perhaps now there is subtitle support as before there was not? EDIT: Just noticed that it no longer reports how much the file was "shrunk" like it did previously. Has that moved somewhere else?

Started tinkering with this. I'm familiar with Nginx Proxy Manager and have a purchased domain. However, no matter what I do it will fail to connect via the FireFox Plugin. Any ideas? EDIT: I think I got it working. Apparently the "v2" after your domain name is VERY important.