Peuuuur Noel

Hi @SimonF You should rename js files by adding random string in filename (like crc32 of the file) or release date as querystring (like /path/to.file.js?20251206) to avoid browser cache issue. Will you also add dynamic app support for LXC? It's pretty much the same as for Docker (check in my old PR #29).

Can you also test this dev version that improve app detection and check if your python app is detected? https://raw.githubusercontent.com/SimonFair/gpustat-unraid/Dev/gpustat.plg (for testing, not production)

But if set to "No" it should use mover.old and not age_mover like in 2023 version? That's what I've done before and ended up to issues after cache was full before mover run. Shares with Cache:Yes were writing on array once minimum free space was reached, then my appdata share (Cache:Only) kept writing on cache on existing files until there was no more space and apps crashed with some corrupted files. Keep in mind that, following unraid manual, Cache:Prefer is the default behavior for appdata, domains and system shares. So if people are not aware of this, their files will be spread across cache and array.

Thanks for your message. I tested but it didn't do what expected. I've no issue with Cache:Yes (as in 2023 version), all files are moved to array when mover runs. That's OK. For Cache:Prefer, files are moved to array based on age, even if I set "Move files off cache based on age" to "No" in Mover Tuning settings (should prevent it, right?). My appdata, domains and system shares are set to Cache:Prefer and when mover runs, VM images, docker and old files are now moved to array which is annoying to have them on HDDs (array) and no longer on SSDs (cache). I want them to always stay on cache, not to move to array. It changes from the original purpose of mover (Mover action: Array->Cache) and from the 2023 version (all files remain on cache, old files are not moved to array). Also, in settings, shouldn't Cache:Yes/No/Only/Prefer be updated to new names to avoid mistakes and for new unraid users (from 6.12) started after these changes? Yes = Primary: [Pool name], Secondary: Array, Mover action: Primary->Secondary No = Primary: Array, Secondary: none, Mover action: not used Only = Primary: [Pool name], Secondary: none, Mover action: not used Prefer = Primary: [Pool name], Secondary: Array, Mover action: Secondary->Primary

I've got multiple shares with primary on cache and secondary on array. Share A is cache preferred, when mover runs (daily, threshold), if files are on array, they are moved to cache (if enough space). Share B will write to cache then move to array when mover runs (daily, threshold). I started with cache only on share A but ended up with an problem when cache was full before mover ran and share A was not able to write data. I set to cache preferred to avoid this issue. If cache is full, shares A and B write to array, then when mover runs (cron+threshold) files on B are moved from cache to array and files on A moved from array to cache. It works like this on 2023 version, but on 2024 version, for shares with cache set to preferred, files are moved to array based on age. I want them to stay on cache if set to preferred. Maybe i'm wrong in my usage of this version of this plugin.

I'm trying to keep all files on cache for shares with cache preferred and write on array if there is no more space on cache (if full before mover runs). In 2023 version, older files was not moved to array (only array to cache if enough space).

Hi, I've setup a share with primary on cache, secondary on array and cache mode on "Prefer/Array->Cache" because I prefer to keep these data on cache (SSD) and overflow on array (HDD) if not enough space. On previous version (last 2023.12.19), mover move data from array to cache if enough space, but with this new version (current 2024-08-01), mover smart move data based on age to array. Is there a way to prevent mover to move data from cache to array like before?

No, PushAPI only works over HTTPS connections because your browser send key and endpoint to the server. These data must not be retrieved by anyone otherwise you could get easily spammed. If you have HTTPS when accessed remotely, you can register your browser from this way. No need to be on the same network or locally to receive notification or register your browser.

Yes, to use browser built in notification system. Mostly for people who don't want to use third party apps like Discord, Slack, Telegram, etc.

Web Push Notification Agent plugin for Unraid This plugin adds browser push notifications to your Unraid server. Works like other notification agents. Prerequisites: Unraid version 6.12+ WebUI over HTTPS connection with valid certificate. Your server must have access to internet (notifications will be send to your devices through push service. Both your Unraid and devices must have access to internet. No need to keep Unraid WebUI open). Usage: Browse the Unraid notifications settings page (just after SMTP Settings) with the device you want to receive notifications on. Click on "Request permission and register" button to allow notifications on your current browser. On desktop: Your browser must be open to receive notifications, otherwise they will be pending until opened. On mobile devices: To enable push notifications on Apple iPhone/iPad, add Unraid notifications settings page to the Home Screen. Notification may not arrive instantly. It will depend on several factors: OS deep sleep, power management profile, frozen application when idle, battery level, network usage, ... and the way notifications are implemented (see this comment for Android on Chromium Issue Tracker). Browser compatibility: Works on: Desktop Chromium based Chrome 50+ Vivaldi 6+ Edge 17+ Opera 42+ Firefox 44+ Safari 16.4+ Mobile (Android) Chromium based Chrome 124+ Vivaldi 6+ Opera 80+ (not Opera Mini) Samsung Internet 24+ Firefox 125+ Not tested on: Mobile (Apple) Safari I don't have access to iPhone/iPad devices, so I can't test on them. Would be great if you could report any issues with these devices. https://github.com/Peuuuur-Noel/unraid-web-push-notification

Hi, I cannot access to MFA Management in my Unraid.net account if I click on link to Unraid.net account from connect plugin. When I click on MFA management link in account page, page go back to account homepage. How to reproduce: 1. Click on "Manage Unraid.net Account" from connect plugin (top right in server Web UI). 2. Login to Unraid Account. 3. Click on "Manage Multi-factor". 4. Page will go back to account home page. Issue on Firefox and Chromelike browsers. No issue if I use https://account.unraid.net url. Looks like to be linked to the "Go Back to <server>" feature.

For disks you will find data in "/var/local/emhttp/disks.ini" and for others (CPU, MB, etc.), the command/program "sensors".

Code in .page (next to ---) is directly included in page body. So don't add <html>, <head> and <body> tags in your code.

You can try to post the screenshot of the inspector on the plex forum, maybe the moderator will have an idea about it.

@Jase If it was a driver or GC related issue, I think you should also have this same issue on local web client and desktop/tv/mobile app. They use same API calls to your plex server. Just to rule out this possibility, have you tried clearing browser cache or testing in private browsing? (I know it sounds stupid but sometimes it solves connection issue). Like the plex forum moderator on the post you linked below, I also see a client disconnect in your logs.