Shu

Here is what I have done now Get new Claim Code Enter Claim code into docker settings and set CLAIM_SERVER to "yes" This correctly claims the server I do still get this error Change CLAIM_SERVER to "no" and restart container No issues so far with an unclaimed server (thank you!!)

I have an issue where my plex server loses its claim after each restart. This started shortly after I did the reset password and log out of all devices - I had no issue with that process (other than needing to remember to use /web for my url). My docker container is a couple years old and I noticed the logs complaining about a CLAIM_SERVER variable not being set. I compared it to the current available version and added CLAIM_SERVER and it did not make a difference. I also notice the log complaining about: I tried deleted my preferences.xml file but no change. I did try the official Plex version and I didn't seem to have an issue with that container but I don't want to switch (nor do I know how to safely switch). Currently, I can either claim the server locally from /web or I can enter a new claim code but both options only work until the container restarts. I do get this in my logs but it doesn't appear with a new claim code entered:

I was experiencing this issue this morning. I went to the keys page and it didn't work immediately. After a few minutes, it did work. I went to the keys page a couple of times and I also poked around my other settings (and enabled MFA!). All good now for me (for now)

When I read it, I found the text to the right confusing. The longer description inside is fine, in my opinion

Yes, sorry haha - the next alongside the setting; not the popup description inside

Yes, sorry for the confusion. If it's helpful, here's what I'd put forth: Disable Mover running on a schedule - "Setting to Yes disables Mover from running automatically" Test Mode (dry run): - "Setting to Yes enables Test Mode" Validate input filenames to prevent attacks - "Setting to No disables validation of filenames" Feel free to copy, modify, or ignore. Thank you, @Masterwishx!

@Masterwishx Can this helper text be updated for clarity? A standard format could be " Setting to Yes effectively disables the plugin schedule" Specifically for the test (dry run) mode; the current help text makes it sound like setting to No would disable the plugin but that's counterintuitive to what "Test Mode: No" reads as

Thank you for the reply. I didn't add the port forward on the router side; just within the docker config area. I've now removed 12345 from VPN_OUTPUT_PORTS. Though, when I tried IPLeak(dot)net with 12345 in that ouput field, I only saw my exit vpn and port - do you think it's still the case where I should not have it? I want to make sure I'm easily connectable by peers (and safely connectable) Edit: I've read that PIA does the port-forwarding within the vpn-config-file automatically but I don't think AirVPN has something similar - that's part of the reason I'm wondering if there's some manual setup I have to do (other than enable the port forward option on AirVPN's side and set my qBit to use that same port)

Can I get a sanity check on port-forwarding? I use AirVPN and I have my wg0 config file placed in the right folder and my qbit set to the same port as I set in AirVPN's site, not the configuration file (12345, for example). When I check canyouseeme(dot)org on a browser that I route through qbit, it shows my exit vpn but it says port 12345 is closed. The same is true when I go to AirVPN's port page and 'test' the port - connection refused. Do I need to add 12345 to my VPN_OUTPUT_PORTS field? I looked at the VPN FAQs and only saw Q27 where it was talking about accessing other routed containers on my lan (though, I'm able to do so with their WebUI ports on my VPN_INPUT_PORTS field, not ouput). I tested adding 12345 to my VPN_OUTPUT_PORTS field and canyouseeme(dot)org says I'm good now. I checked IPLeak(dot)net and it only showed my exit IP and my forwarded port (though, it showed the same forwarded port even before I added 12345 to my output variable). I want to make sure I'm able to seed as many Linux isos as possible. Thanks

> setting to Yes effectively disables this plugin

edit2: although, things could be clearer by changing pwm-fan to pwm-cpu-fan... ---- edit: nevermind, I believe this is not necessary as the log now shows two distinct entries for - pwm-fan - pwm-hdd-fan ---- original: @alturismo, for the PWM fan plugin, would you consider adding the fan number to the log? I have both CPU and HDD fan enabled but the log just reads

I'm getting the nearly the same...numbers listed from 1 to 1000 (each a new line). Mine are fully left-aligned whereas yours seem to be nested under the "Move files that are...:

What kind of hardware are you looking to change and what would you be bringing over from your current system?

I did not. I abandoned the container and now use Notion (cloud)

So is the process (high level) Take out parity drives Install new drives in parity drive slots Rebuild parity Let finish Take out data drives Install old parity drives as new data drives Rebuild data drives I'm thinking it's fairly safe to do the two parity drives at once, right? Then data drives will be 'safest' one at a time?

I am in a situation where my server can only fit 8 hdds and I currently have 2 14tb parity drives and 6 data drives (so I'm full). I just bought two 16tb drives to install. From my understanding, would I do the following: Stop the array Unassign the data drive #1 (can/should I do this for both drives at once?) Start the array (data drive should be showing as 'Not installed') Stop the array again Power down Take out the old drive(s) Install the new drive(s) Power on Stop the array Unassign the parity drive(s) Assign the new drive(s) in the parity slot Assign the old parity drive(s) in the slot(s) of the old data(s) drive being replaced Go to the Main > Array Operation > Copy button check Yes After the copy is done, I start the array to do the "Data Rebuild" Check yes If I do this for one drive at a time, then repeat this exact same procedure for the second drive? Or do I start the second drive at a different step? I was reading the docs and I was a bit confused by this paragraph for Parity Swap: If it would be much more helpful, I could say that my computer can fit more than 8 drives (definitely 1 more but maybe even both new drives). I would need to buy another molex to sata splitter and I'd have to temporarily connect my hdd directly to the mobo as my HBA is at capacity. Much appreciated

Perhaps the errors on the screen I saw didn't get mirrored to the syslog; I'll make sure to take a picture next time. All is seemingly fine now - maybe it was a cosmic bit flip. I'll come back if it happens again, hopefully next time with more helpful information (though, hopefully there is no next time)

All is working fine now, so far. I was able to get in eventually. I was hoping something in the diags would point to the cause for this crash. Would booting in safe mode tell me more?

Been running well for more than a month but started having issues accessing the UI from both WAN & LAN but my containers were still working (I even tried my local IP from a firefox container running on my machine. The login page loaded but signing in just kept spinning then future attempts didn't even show the login page). Later in the night, I noticed my dockers were unresponsive (no Home Assistant, for example). Plugged a monitor into my machine and saw the CLI with weird text I assume were errors. I couldn't figure out how to reboot (I wasn't sure if I was logged in or not but couldn't figure out how to login if I wasn't). Did a hard reset, nothing Unraid-related showed after my BIOS posted. After another unsuccessful hard reset, I went into the bios to confirm boot option (it was correct) and I changed boot wait time from 3s to 10s. Save & Reset then Unraid started to load/show. Attached diags. shuunraid-diagnostics-20231019-2111.zip

Facing the exact same issue - did you ever find a fix?

After setup, I am getting a The server is overloaded or down for maintenance. Please try again later. error notification when loading the webpage. Any one else getting this? The only errors I'm getting on on the logs are these two: ERROR StatusConsoleListener Unable to locate appender "CONSOLE" for logger config "io.ktor" ERROR StatusConsoleListener Unable to locate appender "CONSOLE" for logger config "jetbrains.hosted.entityBro"

I got it working with NginxProxyManager + Cloudflare Tunnel (ddns). I followed my normal procedure as when adding any other service - nothing special for youtracker. Is your container running properly? The container stopped after install due to incorrect appdata permissions (fixed with the previous post)

I got this working by running "chmod 777 -R /mnt/user/appdata/YouTrack" and then "chown -R nobody:users /mnt/user/appdata/YouTrack" Not entirely sure if this second command (chown) is needed but I did it to keep in line with the rest of my appdata folders.

Did you ever get this setup? I'm hoping to reach a similar goal but not sure how to do so

*TFW it takes a SysAdmin to tell you "Have you tried turning it off and on again?"* THANK YOU. That worked haha