XCrownedClownsX

Data Volume Monitor — Network Usage, Thresholds, Notifications, and ActionsSince the original Data Volume Monitor plugin has been deprecated, I decided to take over maintenance by enhancing and continuing it. I wanted to keep it available for the Unraid community while improving its reliability, updating the backend, and making the settings easier to use. The first stable release is 2026.11.04.11. Data Volume Monitor uses vnStat to track network interface usage. It displays traffic reports in Unraid and lets you configure notifications and actions when your data usage exceeds a threshold or returns to normal. What it can doDisplay inbound and outbound usage for five-minute, hourly, daily, monthly, and yearly periods. Show traffic information on the plugin page, Dashboard, and footer. Configure separate inbound and outbound thresholds for the primary interface. Configure six additional threshold rules for secondary interfaces. Send notifications when limits are exceeded or reset. Stop or start selected Docker containers. Disconnect or reconnect selected VM network interfaces. Run custom functions for more advanced actions. Preserve traffic history across normal reboots when database persistence is enabled. Match virtual interfaces to Docker containers and VMs where supported. Traffic accounting is based on network interfaces. Docker and VM matching helps identify those interfaces; it does not provide independent per-application traffic accounting. Installation In Unraid, open Plugins → Install Plugin and paste: https://raw.githubusercontent.com/alexphillips-dev/Data-Volume-Monitor/main/plugin/dvm.plgThe manifest declares a minimum of Unraid 6.8.3, and the packages target x86_64. Not every Unraid version has been tested. After installation, open Settings → Data Volume Monitor. The settings page displays the installed plugin version, release channel, and vnStat backend version. Migrating from the original pluginBack up your settings, custom scripts, and newest stopped traffic database before removing the original plugin. Keep those backups outside its plugin directories. Removing the original plugin can delete its settings and traffic history. Do not install this continuation alongside the original Data Volume Monitor plugin or Network Stats, because they share vnStat service/database ownership. Migration from the original plugin is not automatic. Please follow the guide before uninstalling anything: Migration from the original plugin If you already use this continuation and want to switch between Stable and Development, follow the in-place channel-switch procedure. Do not uninstall to switch channels. Installation and release channels Documentation and supportGitHub repository Wiki and user guides Stable release and release notes Bug reports, feature requests, and configuration help Feedback, suggestions, and testing reports are welcome here or through GitHub. When reporting a problem, please include your plugin version/channel, Unraid version, vnStat backend version, steps to reproduce, and any relevant error message. Remove passwords, tokens, server names, public IP addresses, and other private information from screenshots and logs. Automated validation includes 142 Python tests, additional PHP and JavaScript fixtures, native vnStat compatibility tests, and package verification. These checks do not replace live Unraid installation, native theme, workload-action, or reboot testing. A host acceptance checklist is available for anyone helping test those areas. Fixes and improvements included in this releaseThe following is the cumulative list of fixes and improvements made while developing this continuation, rather than only the changes in the final development build. Configuration editor Restricted editing to supported configuration files, with checks for directory traversal, symlinks, unsupported file types, and paths outside the permitted locations. Fixed stale editor responses that could load the wrong content after switching files. Added save-identity checks so one file’s content cannot be saved into another after a file switch. Improved handling of partial or failed paired saves, including restoration of previous contents and file permissions on handled failures. Preserved support for intentional empty-file saves. Added clearer error messages for failed reads and saves. Added unsaved-change protection when switching files, cancelling, or leaving the editor. Preserved edits made while a save request is still running. Thresholds, notifications, and actions Fixed failed or unavailable threshold queries being confused with exceeded limits. Prevented query failures from triggering threshold actions or appearing as confirmed healthy data. Serialized concurrent notification checks and handled lock-acquisition failures. Fixed evaluation and aggregation of all six secondary threshold rules, including multiple rules targeting the same interface, direction, and period. Added checks for failed VM lookup, missing network interfaces, and failed disconnect/reconnect commands before reporting success. Corrected the custom-alarm 45-minute schedule across hour boundaries. Made Service Check diagnostic only, without running configured workload actions or changing notification/action state. Added a separate, confirmed Test Configured Actions control. Added recorded action outcomes for individual rules and action components, including failed and interrupted attempts. Added deliberate retries for recorded failed components, with checks against the current configuration, scripts, and threshold state. Prevented stale action results from automatically retrying operations. Added a validated custom-alarm example. Monitoring, reports, and interface matching Prevented overlapping refresh requests and added finite request timeouts. Preserved the last complete measurements when a refresh fails or returns incomplete data. Added visible stale and unavailable states, with recovery when valid data returns. Prevented late responses from updating pages after navigation. Resumed polling correctly after browser back/forward cache restoration. Kept valid traffic measurements available when only the threshold evaluation fails. Corrected combined interface/service filtering and exclusions. Preserved Docker and VM names containing spaces or special characters during matching and filtering. Improved virtual-interface matching checks around peer indexes and bridge interfaces. Escaped interface names, service labels, and report text. Improved generated image names and image URL handling. Added content-based cache invalidation for shipped UI scripts. Service, storage, backup, and recovery Improved propagation of service start/stop, installer, reset, wrapper, and package-removal failures before dependent operations continue. Honored effective custom database and PID-file paths throughout service checks, persistence, restoration, and resets. Prevented database/PID path changes through the editor while the service is running. Preserved the selected database location during configuration and full resets. Added verification of shutdown-hook installation and removal, including supported host-layout differences. Added database backup path/checksum verification. Retained a previous verified backup generation for recovery. Rejected corrupt, incomplete, mismatched, and wrong-path backups. Prevented an invalid current backup from replacing a valid retained generation. Staged restoration before creating the runtime database, reducing the risk of leaving a partial database after a failed copy. Settings and appearance Replaced the long stacked Primary Interface threshold controls with a table matching the Secondary Interface section. Preserved all eight primary rules and their 48 saved threshold, unit, and action fields. Added accessible labels and horizontal scrolling for the primary table on narrow screens. Kept threshold and action controls readable and editable when a limit is disabled. Added live Disabled labels in red, Enabled labels in green, and Invalid labels in red. Matched threshold status validation to whole-number and unsigned 64-bit limits. Preserved saved interfaces and Docker/VM targets when inventory discovery is empty or fails. Clearly identified unavailable saved selections instead of silently replacing them. Distinguished an empty inventory from a failed discovery command. Kept the traffic overview visible while placing detailed reports in a labeled section that starts collapsed. Added spacing between inbound/outbound footer values and colored the direction arrows. Updated the plugin artwork in both the Plugins listing and Settings tile. vnStat backend Upgraded the bundled vnstat, vnstatd, and vnstati executables from 2.12 to 2.14. Added a reproducible dependency build using verified signed upstream source. Recorded build inputs, executable hashes, runtime-library requirements, and compatibility information. Retained required backend license and documentation files. Documented newer vnStat configuration options while preserving DVM defaults and saved settings. Tested reading a vnStat 2.12 database with 2.14 while preserving its traffic, schema, and alias data. Tested threshold boundaries across periods, traffic directions, and unit modes. Tested invalid input, overflow, unavailable data, and custom effective paths. Exercised all three backend executables, six PNG output modes, JSON/XML escaping, and PHP text/image/combined reports in isolated fixtures. Packaging, release channels, and documentation Updated active plugin paths, installer/download/update URLs, and support links for this continuation. Added installer conflict checks for the original plugin and Network Stats. Added separate Stable and Development channels, with each installation retaining its own update URLs. Added installed version/channel information to the settings page. Added guarded release preparation, version-ordering checks, concurrent-edit detection, and transactional generated-file updates. Improved build-failure handling so existing deliverables survive validation, source-read, and handled publication failures. Preserved executable script permissions. Added package inventory, permission, checksum, provenance, and deterministic-rebuild checks. Kept local tool configuration, caches, credentials, runtime databases, logs, temporary files, and diagnostic exports out of tracked distribution files. Expanded the README and wiki with setup, migration, thresholds, notifications, actions, reports, configuration editing, backup/recovery, troubleshooting, and host-testing guidance. Added dedicated GitHub forms for bug reports, feature requests, configuration help, and documentation issues.

I’ve released Parity Check Tuning Plus, an independently maintained continuation of Parity Check Tuning with fixes, improved operation handling, and expanded language support. The plugin helps you control when long-running array operations run, keeping parity work within a schedule that suits your server. FeaturesSplit scheduled, manual, or automatic parity checks into daily, weekly, or custom increments. Optionally apply increment scheduling to parity sync, data rebuilds, and disk clearing. Pause operations while mover or supported appdata backup tasks are running. Pause and resume around disk temperature limits, with an optional critical-temperature shutdown setting. View extended parity history, including elapsed time, active runtime, and increment counts. Investigate reported parity-error sectors with the partial-check Assistant. Offline translations for 42 language variants, including right-to-left layouts. The first stable release includes fixes for mover detection, unexpected background notifications, scheduling boundaries, temperature handling, restart validation, history accounting, Assistant controls, and Settings alignment. It also addresses the misleading “Canceled” notification appearing after a successfully completed parity check. InstallationOpen Plugins > Install Plugin and paste this stable installation URL: https://raw.githubusercontent.com/alexphillips-dev/Parity-Check-Tuning-Plus/main/parity.check.tuning.plus.plgConfigure the plugin under Settings > Scheduler. The Assistant is available under Tools > Parity Check Tuning Plus. Switching from the previous pluginFinish any active array operation, then remove the previous parity tuning plugin before installing Plus. Plus uses separate settings and does not automatically import the previous plugin’s configuration or operation state, so review and recreate your preferred settings after installation. Unraid’s native cumulative parity-check scheduling and Plus increment scheduling should not both manage the same operation. Partial checks are intended for investigation and do not replace a full parity check. Project and documentationGitHub repository Wiki and setup guide Installation and migration Complete release notes Report a bug or request a feature Feedback, bug reports, and translation corrections are welcome. When reporting a problem, please include your Unraid version, plugin version, relevant settings, and steps to reproduce it. Remove private information from any logs or screenshots before sharing.

The wording is confusing—“cannot be unlocked here” means there isn’t an unlock button or setting for these safety blocks. I checked your diagnostics. All four folders are blocked because an installed Docker container has the AppData root containing those folders mapped into it. The plugin therefore cannot treat those folders as safely unused, even if their original applications have been removed. To identify the container: Click Details on any blocked row. Expand Specific container mounts. This shows the container name and host paths responsible. Review that container’s path mappings. If it needs those mappings, leave them in place—the folders will remain protected. If a mapping is obsolete or unnecessarily includes the whole AppData root, correct it only after confirming what the container needs, apply the change, and rescan. Simply stopping the container will not clear the protection, because stopped containers’ mappings are checked too. Changing Safe Mode will not bypass it either. If you’re unsure why that container needs the mapping, share a screenshot of Specific container mounts, with any private names or paths obscured, and we can help review it before you change anything.

Thanks for sending the bundle and confirming the browser/theme details. It captured repeated Docker list rebuilds, which can restart the native autostart-switch animations. I corrected the deferred container-detail merge that could trigger those rebuilds. This fix applies with or without Aurora. Please test main/stable 2026.10.30.05: Go to Plugins → Check for Updates, update FolderView Plus, and confirm the installed version. Hard-refresh Docker with Ctrl+F5 or Ctrl+Shift+R (Cmd+Shift+R on macOS). Leave Docker idle for 1–2 minutes, then check Basic, Advanced and Privacy views, your usual Start/Stop and WebUI actions, and folder membership. The correction preserves current container identities, membership facts and newer state while details load, and ignores stale details for removed or replaced containers. This release also fixes support-bundle false positives caused by version numbers and includes the Settings button/icon, tree-control and duplicate-heading corrections. If the list still rebuilds or the switches keep animating, use Docker → Tools → Capture page diagnostics while it is happening, before refreshing again. Then export a fresh sanitized support bundle from Settings → FolderView Plus → Advanced → Diagnostics. Please review it before sharing and include the browser, affected view and a short clip if possible.

@Revan335 Unraid theme I was adding compatibility for.

@Ritmjunk @karaa Thanks for reporting this, and sorry for the trouble. 2026.10.27.05 included changes intended to fix the Docker page bouncing I reproduced with Aurora. Since removing or rolling back FolderView Plus clears your glitches, I’m treating this as a likely regression in that update. Please stay on your working version for now. Could you both share: - Your browser and theme, including the Aurora version if you use it. - Which page is affected, and whether Docker is in Basic or Advanced view. - The last FolderView Plus version that worked correctly. @karaa Could you also confirm your Unraid version? If you still have 2026.10.27.05 installed, please capture the issue before refreshing. Can both of you on the Docker tab, use Tools → Capture page diagnostics at the bottom, then export a fresh sanitized support bundle from Settings → FolderView Plus → Advanced → Diagnostics. I’ll follow up here once I have a verified correction.

Please update to FolderView Plus 2026.10.15.07. This includes fixes targeting the Docker UI issue you reported: Correctly match completed container actions when Unraid’s native container ID and the API-provided ID use different formats. Refresh container status and clear loading indicators for both standalone containers and containers inside folders. Update existing rows while preserving their context-menu handlers, so subsequent actions remain available without refreshing the page. These fixes cover Start, Stop, Pause, Resume, and Restart. Update through Plugins → Check for Updates, confirm FolderView Plus shows 2026.10.15.07, then hard-refresh the Docker and Dashboard pages with Ctrl+F5. Please try Start/Stop a couple of times without refreshing between actions and check that the spinner clears, the status changes, and the context menu remains usable. The Permissions policy violation: unload is not allowed warning in dynamix.js was not confirmed as the cause. If it still appears, please check whether the spinner/menu issue persists. If the problem persists, please send: Your Unraid version, Chrome version, and installed FolderView Plus version. The exact steps: which action hangs, whether the container is standalone or inside an expanded/collapsed folder, and whether its actual running state changes successfully. While the problem is visible, before pressing F5, use Docker → Tools → Capture page diagnostics. Then go to Settings → FolderView Plus → Advanced → Diagnostics, preview and export a fresh sanitized support bundle. Any console errors and their stack traces from that attempt, plus a screenshot or short recording if helpful. Please redact private container names, addresses, paths, and other identifying details. The Diagnostics and Support guide explains the capture/export steps. Fresh diagnostics from the updated version will help us identify any remaining failures.

@kikkawa Thanks for the report, I'll take a look to see what's going on.

Please update to FolderView Plus 2026.10.13.06, confirm that version under Plugins, then hard-refresh the Unraid webGUI with Ctrl+F5 and repeat the action that failed. This release includes these related fixes: Corrected Unraid CSRF token handling for plugin requests that make changes, while retaining Unraid’s CSRF checks and the plugin’s token/nonce protection. Changed custom-icon uploads to use form-encoded requests, with larger files split into individually authorized parts. This addresses the upload timeouts we reproduced during investigation. Raised the icon limit to 16 MB without requiring PHP or Nginx configuration changes. Fixed deleting the currently selected custom icon so all folder-editor previews return to the default icon. Release notes for 2026.10.13.06 If it still fails, please reproduce it once on the updated version and provide: Exact steps and location: which page/action fails, and whether it is a FolderView Plus action or Unraid’s native File Manager. Include the approximate time of the failure. A fresh sanitized support bundle: open Settings → FolderView Plus → Advanced → Diagnostics, review the sanitized preview, and export it after reproducing the problem, preferably in the same browser tab. Chrome DevTools evidence: press F12, enable Preserve log in Network, then reproduce the failure. Share any relevant Console errors and the failed request’s endpoint path, method, HTTP status, Response, and Timing. Include the full displayed error and any support/trace code. Matching syslog lines: any fresh missing csrf_token, Nginx, PHP-FPM, FastCGI, or upstream errors around that time. If nothing appears, please say so. Please redact server addresses, personal paths/names, cookies, tokens, and authorization details from screenshots or logs. There’s no need to share request payloads or a full HAR export. That will let me determine whether the remaining failure is in the plugin’s request handling, the Unraid session/security checks, or another endpoint.

Yes ill look at this issue and let you know if i need more information.

FolderView Plus 2026.10.07.16 is now available — introducing Quick finder!This update adds Quick finder to the Docker and VM tabs, making it easier to find folders, containers, and virtual machines—especially when you have a lot of items organized into nested folders. Click the magnifying glass immediately to the left of the Basic/Advanced toggle and start typing. Search matches names and containing folder paths, including items inside collapsed nested folders. Results appear only after you start typing. On the Docker tab, you can switch between All, Folders, and Containers. Folder and container results have separate, collapsible sections with result counts, your configured icons, and container status indicators. Quick finder brings the relevant controls into the search results:Click a result to reveal and highlight it in the normal view, expanding its containing folders as needed. Focus folder to narrow the view to that folder. Edit folder to open its settings. Use the familiar Docker WebUI, console, and logs icons when those actions are available. Use the three-dot menu to access the existing folder or member actions. For example, if you know which container you need but cannot remember where you put it, type its name and jump straight to it. You can also search a folder path to find the containers organized under that branch, or open an application’s WebUI directly from its result. Unavailable shortcuts remain disabled, so the results reflect what Unraid can currently do. The search follows the tab you’re usingOn the VM tab, Quick finder searches VM folders and virtual machines. Its filters and available actions follow the VM view, including logs and the native VM menu where available. The layout supports desktop and phone screens, light and dark themes, and keyboard navigation. Use the arrow keys to select a result, Enter to reveal it, and Escape to close search. Search results also follow your Privacy settings, masking names, identifying icons, and folder paths when selected. Your typed query stays readable and is temporary—it is not saved or included in diagnostics. Also included in this updateThere is now a Report issue on GitHub button beside Export support bundle under Settings → Advanced → Diagnostics. It opens the issue forms in a separate tab, making it easier to report a problem while keeping your diagnostics available. Support bundles still need to be reviewed and attached manually. This release also includes search interaction fixes, browser layout improvements, and updated documentation. Your existing folders, assignments, preferences, and backup schedules are preserved. Full release notes · Quick finder documentation Give it a try and let me know how it works with your setup! If you encounter a problem, include your Unraid version, browser, FolderView Plus version, and a sanitized support bundle where relevant.

That’s interesting and most likely a bug. Can you post your support bundle from diagnostics or dm it to me so I can take a further look?

Glad it's resolved; sorry that was driving you up a wall lol. Please continue to test, and if you find any further issues, please let me know.

FolderView Plus 2026.09.17.03 includes a fix for the empty-JSON upload error. If the normal upload returns an empty response, the plugin now automatically tries its alternative upload method. Please update to the latest stable version, hard-refresh the Unraid webGUI, and try uploading the same image again. If it still fails, please share the new error message, the image’s file type and size, and a fresh sanitized support bundle.

The fixes are now available in FolderView Plus 2026.09.17.03: Added Edit folder defaults links for Docker and VMs, including defaults imported from FolderView3. Fixed hover previews on computers that also have a touchscreen. Fixed stopped-icon grayscale in Docker previews. Fixed mixed folder/container positions being lost after refresh. Fixed Dashboard cards staying narrow instead of filling the available widget width. Please update to the latest stable version and hard-refresh the Unraid webGUI. Editing defaults affects future folders; existing folders stay unchanged unless you explicitly apply the defaults to them. If anything still misbehaves, please share a fresh sanitized support bundle and a screenshot of the affected setting or layout.