Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

UnraidTobias

Members
  • Joined

  • Last visited

  1. Thx. I Just checked those two scrips on my Side: usr/local/emhttp/plugins/dynamix/scripts/outgoingproxy /usr/local/emhttp/plugins/dynamix/scripts/wg_config I've none of those services configured or in use (checked in settings, there are NOT Setup/configured/active) at all. And...I am usig tailscale anyway instead. - So i think those have nothing to-do with it.
  2. I also can subscribe, facing the same issue. Whats the point of this output? Here's mine as well: # ls -ail /usr/local/emhttp/plugins/dynamix/script s total 176 100 drwxr-xr-x 1 root root 80 Nov 3 20:40 ./ 99 drwxr-xr-x 1 root root 180 Nov 3 20:40 ../ 6940 -rwxr-xr-x 1 root root 434 Nov 16 2023 agent* 6941 -rwxr-xr-x 1 root root 229 Nov 16 2023 bootmode* 6942 -rwxr-xr-x 1 root root 420 Nov 16 2023 btrfs_balance* 6943 -rwxr-xr-x 1 root root 330 Aug 15 21:24 btrfs_check* 6944 -rwxr-xr-x 1 root root 819 Nov 16 2023 btrfs_scrub* 6945 -rw-r--r-- 1 root root 1739 Aug 18 20:23 check.source 6946 -rwxr-xr-x 1 root root 775 Nov 16 2023 console* 6947 -rwxr-xr-x 1 root root 39251 Oct 15 06:42 diagnostics* 6948 -rwxr-xr-x 1 root root 774 Nov 16 2023 disk_size* 6949 -rwxr-xr-x 1 root root 489 Nov 16 2023 emcmd* 6950 -rwxr-xr-x 1 root root 728 Feb 16 2025 error_interfaces * 6951 -rwxr-xr-x 1 root root 236 Aug 15 21:24 exfat_check* 6952 -rwxr-xr-x 1 root root 226 Aug 15 21:24 ext_check* 6953 -rwxr-xr-x 1 root root 13602 Apr 4 2025 feedback* 6954 -rwxr-xr-x 1 root root 1693 Nov 16 2023 flash_backup* 6955 -rwxr-xr-x 1 root root 577 Nov 16 2023 ftpusers* 6956 -rwxr-xr-x 1 root root 2114 Aug 14 07:44 install_key* 6957 -rwxr-xr-x 1 root root 15620 Jun 29 2024 monitor* 6958 -rwxr-xr-x 1 root root 6538 Feb 26 2025 netconfig* 6959 -rwxr-xr-x 1 root root 2514 Aug 14 07:44 newperms* 6960 -rwxr-xr-x 1 root root 849 Jan 9 2025 nfsSettings* 6961 -rwxr-xr-x 1 root root 9915 Feb 16 2025 notify* 6962 -rwxr-xr-x 1 root root 229 Aug 15 21:24 ntfs_check* 6963 -rwxr-xr-x 1 root root 1282 Apr 22 2025 open_ssl* 6964 -rwxr-xr-x 1 root root 3390 Dec 17 2024 outgoingproxy* 6965 -rwxr-xr-x 1 root root 1154 Nov 16 2023 parity_control* 4159 -rwxr-xr-x 1 root root 8099 Nov 3 20:40 parity_history* 6966 -rwxr-xr-x 1 root root 3150 Feb 5 2024 parity_history.o rig* 6967 -rwxr-xr-x 1 root root 141 Dec 29 2023 powermode* 6968 -rwxr-xr-x 1 root root 255 Aug 15 21:24 reiserfs_check* 6969 -rwxr-xr-x 1 root root 336 May 10 10:32 reload_services* 6970 -rwxr-xr-x 1 root root 649 Feb 5 2024 replace_key_job* 6971 -rwxr-xr-x 1 root root 677 Mar 26 2025 restore_favorite s* 6972 -rwxr-xr-x 1 root root 3583 Feb 16 2024 rsyslog_config* 6973 -rwxr-xr-x 1 root root 1437 Nov 16 2023 run_cmd* 6974 -rwxr-xr-x 1 root root 4582 Jun 23 19:24 select_case* 6975 -rwxr-xr-x 1 root root 4182 Jul 16 2024 set_proxy* 6976 -rwxr-xr-x 1 root root 826 Nov 16 2023 share_size* 6977 -rwxr-xr-x 1 root root 269 Jul 27 2024 show_interfaces* 6978 -rwxr-xr-x 1 root root 4035 Aug 14 07:44 ssd_trim* 6979 -rwxr-xr-x 1 root root 8080 Mar 23 2024 statuscheck* 6980 -rwxr-xr-x 1 root root 9897 Oct 15 06:42 system_informati on* 6981 -rwxr-xr-x 1 root root 1771 Apr 22 2025 update_access* 6982 -rwxr-xr-x 1 root root 541 May 30 20:22 update_services* 6983 -rwxr-xr-x 1 root root 1602 Nov 16 2023 upnp_poller* 6984 -rwxr-xr-x 1 root root 104 Nov 16 2023 upnp_poller_star t* 6985 -rwxr-xr-x 1 root root 1350 May 31 17:54 upnp_port* 6986 -rwxr-xr-x 1 root root 2304 Feb 5 2024 wg_config* 6987 -rwxr-xr-x 1 root root 1649 Mar 31 2025 wireless* 6988 -rwxr-xr-x 1 root root 252 Aug 15 21:24 xfs_check* 6989 -rwxr-xr-x 1 root root 518 Jul 30 19:52 zfs_scrub*
  3. @Espressomatic Sure, would be great if you can do, thx
  4. @Squid May you share the repository so forks/improvements can be added? Or update the plugin? Please? Thx!
  5. Can you please also add the auto-unmount option? If a device goes offline and stays offline, to the script as well? For Unraid7. Cause in my case, UA, does NOT un- mount the device if it goes offline and stays of line...
  6. @Squid The save button is permanently disabled on my side, please make sure the elements are accessible by jQuery by waiting for the DOM to be fully loaded ($(document).ready()). Like so: <textarea id="UnraidNotes" style="font-family:Courier New; width:90%; margin-left:5%" rows="20" placeholder="Enter Notes Here"></textarea> <br><br> <center> <input id="saveButton" type="button" value="SAVE" disabled /> </center> <script> $(document).ready(function() { // Enable save button when textarea content changes $('#UnraidNotes').on('input', function() { $('#saveButton').prop('disabled', false); }); // Save changes function function saveChanges() { alert('Changes saved!'); } // Bind the save button click event $('#saveButton').on('click', saveChanges); }); </script>
  7. @Iker Please fix and see https://forums.unraid.net/topic/151174-zfs-snapshot-delete-destroy-dataset-is-busy-operation-not-permitted/ Thank you
  8. Thanks for your reply, Yes i´ll do so now, ill use rsync -av --ignore-existing --size-only --update /mnt/cache/ /mnt/disk1/ And remove the source files from cache afterwards once ... ..but still i am not sure if mover should be able to handle then new files between the zfs-drives/datasets keeping the same setup. Do you know more about this maybe?
  9. I am currently on unraid 6.12.14, having a ZFS pool (cache) drive and a HDD drive in Array (disk1). Both are ZFS formatted. I am unable to move files (zfs datasets) from the cache pool to the array drive using the mover. Shares are setup like this: Primary: cache Secondary: Array Mover: Cache -> Array Mover tries to move but reports: Unraid move: file: /mnt/cache/docker/volumes/backingFsBlockDev Unraid move: move_object: /mnt/cache/docker/volumes/backingFsBlockDev File exists (this is kind of ok, if i can remove the already exisiting files on source ?) But it also shows multiple entries like: Unraid move: file: /mnt/cache/appdata/dozzle/users.yml Unraid move: create_parent: /mnt/cache/appdata/dozzle error: Device or resource busy (but there is nothing obvious accessing the device or resource...) I already checked if anything is still accessing the device or resources but there is nothing. Docker and VMs are also disabled of course... I think it is related to the datasets? In general, can someone explaing a bit more about the ZFS Features supported with Unraid 7 and mover, please, like, i am unsure about: I cannot find any explicit info in the changelog if this is solved in Unraid 7. Do you know? Does Unraid 7 support ZFS and mover to 100% already? Does somebody know? Should i update to 7?
  10. I kinda have a similar question, could you maybe help me out?, please see: Thx
  11. I kinda have a similar question, could you maybe help me out?, please see: Thx
  12. SSH into server and run: /etc/rc.d/rc.nginx restart
  13. Hi @Squid, since updating to unraid v 6.12.14, using CA version 2924.11.29 - if i am updating any application via "Action centre" i get the usual modal with headline "Update Application" but inside it there is no text, nothing, no progess/log is visible during updates. I did already restart the server, tried to clear browser caches as well, network console/F12 dev tools shows now errors. How to fix this?
  14. Great. Thank you. I think this will be a huge usability improvement. How are the release circles? Another suggestion: Currently, on initial loading of CA, it shows a loader and refreshes the apps lib (it seems), which takes always a bit. That happens on every load of the frontpage...seems redundant to me. Suggestion: Not automatically doing that on every pageload. Instead: Do it only once (after inital app setup for example) and show, from there on, instead a button "refresh app index" (or similar) to trigger it manually. (Or maybe make it configurable?) Benefit: Improved pageload/speed overall for the whole app/index. Of course also similar solutions would be fine - just avoid the current behaviour, having to "wait" always some seconds after clicking onto "apps" 🙂 thx
  15. @squid Currently, when clicking onto the "support" button of any CA -Entry (after previously having scrolled down the page) it will lead to scolling up the page - even if you open any entry like "project" or "support" from the context menu. Can we somehow avoid that or could you avoid/fix that please? Thanks in advance!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.