dirtymike0330

Does this require adding /tmp in the Transcoder temporary directory of Plex>Settings>Transcoder? I currently have that in mine and I'm not sure why I am getting the (hw) transcode so I know something is working (I believe I initially set this up for using my cpu).

My server restarted about a day ago, after being up for like 3 months, for an unknown reason. Since then, I have had most containers having network issues. Most notable, containers like Prowlarr, Jackett, Arr apps, all reference "443, resource unavailable, connection failed" etc etc. Most of them make some kind of network reference. I'm not sure what is going on at this point. I restarted the machine, restarted the router (which had a pending firmware update) with no luck. Everything was working fine prior to the restart and I made no changes. I will include some logs from the indexer apps, my ip table if anything looks wonky with that, and a diag zip. Thanks for any help. Hastebin: Send and Save Text or Code Snippets for Free | Toptal® Hastebin: Send and Save Text or Code Snippets for Free | Toptal® luciotti-diagnostics-20220415-2234.zip

Is this anything I need to worry about? 3 sections in the picture: 1 is the warning I am seeing. 2 is the share referenced and 3 is the VM setup. I'm not sure what the warning is implying or if it is a big deal. If it is something I need to change, I'd rather not have to lose or re-do the VM because I am running a game server on it.

I can access my unRAID machine fine and nothing seems to be going wrong, I just want to make sure the attached picture isn't something I need to be concerned about. I only see it when I log onto the web dashboard at forums.unraid.net/my-servers

Ah ok, my apologies, I didn't realize we could do those edits but after looking for that I found the exact solution at Template Edit - thank you

In reference to a github issue I raised, specific to the linuxserver homeassistant docker Github Comment, upon updating homeassistant, multiple mandatory path/to/device fields populate and cause the container to fail to start until I manually delete them. Initially, the dev instructed that I get Docker into author mode and delete the TemplateURL, but then discovered the existence of this thread and the end of TemplateURL in author mode. However, they state that the template sync is turned off on their end. Is there anything I can do on my end to remedy this? I apologize if this needs to be posted elsewhere.

I'm not overly familiar with GitHub, but what is the time frame usually for the develop branch to get merged into a master branch? Or, if there a way with the unRAID docker to switch to using the dev branch instead of master? The latest dev release has a vital upgrade (haven't been able to access my arr apps via reverse proxy address in several days because something in the code had to be renamed) that was released today but it isn't reflecting in unRAID yet. Thanks!

UPDATE: I don't know if the devs pushed any updates, but I have been connected fine for several days now. Solved (on my end anyway). Thanks.

I went to http://tower/log/syslog and added that file - I assume that is what you're referring to? I have my syslog server local folder set to appdata, but I don't actually see any log files in that folder.

I'm not sure how to do that

Hello all - twice in the last week, I lost access to Plex and went to check unRAID and saw that it had done an unclean shutdown and the array was off. I did not lose power at home, as far as I can tell. After the first time, I setup the syslog server and after it happened again today, I downloaded the diagnostic file (attached). Can someone please tell me if they see anything in the log to indicate what is causing the array to stop? I can't really interpret any of it. Thanks. luciotti-diagnostics-20211029-0954.zip syslog

@zspearmint I just wanted to piggyback on this as well: I upgraded my license today from free to Plus and am now getting the "not connected to mothership" error. I have: 1. unraid-api restart 2. Uninstalled/reinstalled plugin 3. Rebooted 4. Made sure to go to tools/registration and download/install the upgrade key No luck.

I upgraded my license today from free to Plus and am now getting the "not connected to mothership" error. I have: 1. unraid-api restart 2. Uninstalled/reinstalled plugin 3. Rebooted 4. Made sure to go to tools/registration and download/install the upgrade key No luck.

I have a Win10 VM spun up for the sole purpose of running a DCS (digital combat simulator) dedicated game server. It works fine, but sometimes when I check it after a few days, I'll find that the server and 2 additional programs I had left running have inexplicably shut down, which makes me think the VM restarted. Is there some kind of auto restart function with VMs that I need to disable? Are there any unRAID plugins that could be restarting my VM without me knowing? (I have win login bypassed on the VM).

This docker has updated twice since I have installed it and every time it updates, the web UI gets broken/inaccessible. What gives? I change no settings - update only.