wizenthorne

Is there another place I should be posting this issue? I was directed to come here.

Action Centre stopped triggering for me. Action Centre no longer triggers on its own. In the Docker tab it correctly displays containers which are ready to update. Pinning an app seems to trigger the Action Centre after a few minutes, but this is the only "fix" I've found. I'm not exactly sure when the issue started but it was sometime after the 7.2.4 update.

Action Centre no longer triggers on its own. In the Docker tab it correctly displays containers which are ready to update. Pinning an app seems to trigger the Action Centre after a few minutes, but this is the only "fix" I've found. I'm not exactly sure when the issue started but it was sometime after the 7.2.4 update. I've done some searching around the forums but couldn't find anyone else with this issue.

Thank you for this! Worked just fine!

Have you have any luck since your last post?

First I want to thank you for putting these install templates together! I am encountering an error that appears as soon as I attempt to load the webpage: We're sorry, but something went wrong. In the log for the maybe_web docker it says: FATAL -- : URI::InvalidURIError (bad URI (is not URI?): "127.0.0.1:6379/1") I already had redis running on that port and if I turn off the redis docker I get a page telling me I need to configure redis, so I am pretty sure it's connecting to redis. I'm just unsure what that error message means. Does anyone have any ideas? When I search those error messages I cannot find anything related to Maybe. EDIT: I ended up having to change the redis url to redis://(Unraid Server IP):6379/1 and switch the Network from maybe-stack to Bridge.

Oh okay, that's good to know. I was unaware they it keeps breaking. I'll check in with the Plex forums. Thank you!

The GPU is set instead of auto. Non-HDR transcoding works fine. Thank you for the response. Do you have any other ideas?

Problem: Transcoding from 4k HDR10 to anything else will trigger the GPU for a moment then it falls back to CPU. Unraid: 7.0.0 GPU: Nvidia RTX 2070 Super Nvidia Driver Version: 565.77 (multi-transcode unlocked with patch) Plex Version: 1.41.4.9463 (running in Docker with GPU passthrough confirmed working) Details: - Plex will successfully transcode multiple 1080p to 720 or any other resolution and shows these transcodes working from the CLI when I run 'watch nvidia-smi' - The 'watch nvidia-smi' monitor will show the Plex transcode briefly when attempting to transcode from 4k HDR to 1080p but after a few seconds the GPU transcode will fall back to CPU and it will disappear from the GPU monitor. - I have tested with both Dolby Vision and non-DV HDR videos. - I have tested with HDR mapping on and off in Plex settings. - Plex is correctly configured to use the Nvidia GPU, shows the proper GPU in the settings, and successfully transcodes 1080p videos using the GPU. Has anyone else been able to get their NVIDIA RTX GPU to transcode from 4k HDR to 1080p? If so, do you have any suggestions for me as to why it keeps falling back to CPU on my machine? I have done extensive searching here and after many hours have been unable to find a solution. Thank you for your time reading this.

Thanks, everyone, for all of your insight into the benefits of using the Tailscale service versus something like Headscale running on Unraid. In the even that the Tailscale servers do go down for a period of time, if devices have already connected, would those connections be maintained until an IP changes on a device? I assume once the DNS is resolved the magicDNS service is no longer required until the IP changes?

Is Headscale going to be discussed at all, or with this partnership is there a plan to allow Tailscale to run self-hosted without needing to phone home or connect to a third-party Tailscale server? Everyone here is a self-hosting enthusiast and while Tailscale is cool, it is not a self-hosted product as far as I can tell.

So I did try rebooting with the internal drive unplugged and reformat the internal drive using UD. Neither solution worked. It would seem my last option is probably to move my files off the external, format, then move them back. Is it possible the problem I'm having is due to the external being formatted to ntfs instead of xfs?

This is what the external that won't mount after a reboot reports.

External had no errors. The internal reported errors. It attempted to fix. Did a reboot. Still not mounting the external. Ran the check again on internal. Still errors so I did the extra step (forgot what it was called) and that fixed it. Rebooted. Still won't automount the external. I'll probably do your suggestions slightly out of order because I don't have anything critical on the internal one so I'll probably just format and see if that fixes the issue without disconnecting it.

Also after I started my array the option to dismount became unavailable until I hit the double-arrow refresh button again. Edit: So It makes me wonder if somehow the array starting is causing the initial mount option to become disabled.