Uleepera

Has anything changed over the last week or two? Both binhex-delugevpn and binhex-jackett are showing up as version not available in the docker tab on Unraid. Using 7.1.4 if it matters.

Understood, I was pointing out that calling people trying to fix it an embarrassment wasn't productive or appreciative of their time/effort. Success aside, my expectation for free software isn't as high as his/hers apparently.

Are you volunteering? Or do you just like to shit talk people who are working for free?

No worries, man, I'll take a peek and see but I haven't used them before.

Not a single change yet. I just wanted to get it back and functional to start. Then I can take a look to see if updates are possible. Check box isn't a bad idea similar in windows to removing anything from microsoft on the service list. I'll poke around later and see.

I accelerated my plans and updated to 7.x this morning. Removed all the old files related to open.files. Max version number is bumped up to 7.99 for now. Let me know if you have success.

It's forked from the most recent release before the repository was pulled. I'm still running 6.12.14 but plan to move up to 7.xx shortly and can retest then. I capped at 6.99 just because I couldn't test it. If you'd like to try in the meantime I can raise the cap? This is my first attempt at anything app releated on here. I'm not sure what protocol for this is.

lol so do I

## [PLUGIN] Unraid Open Files Plugin (Fork) This is a fork of the original **Open Files** plugin for Unraid, originally developed by **BubbaQ** and later maintained by **dlandon**. This version is maintained for archival and utility use, preserving its original functionality while modernizing plugin packaging and structure. --- ### 💡 What It Does This plugin helps diagnose issues with unclean shutdowns by showing what files are open on the array and what processes are holding them. It adds a page to the **Tools** tab in the Unraid web GUI that lets you: - View which files are open and which processes are using them - Stop all array processes cleanly - Identify what’s blocking the array from clean unmounting --- ### 🛠️ Installation Install via the **Unraid web UI**: 1. Go to **Plugins** > **Install Plugin** 2. Paste this URL and click **Install**: `https://raw.githubusercontent.com/Uleepera/unraid-open-files-fork/main/open.files.plg` --- ### 📁 GitHub Repository - **Code**: [https://github.com/Uleepera/unraid-open-files-fork](https://github.com/Uleepera/unraid-open-files-fork) - **Plugin File**: [open.files.plg](https://raw.githubusercontent.com/Uleepera/unraid-open-files-fork/main/open.files.plg) --- ### ⚖️ License This plugin is released under the **GNU GPL v2.0** license. --- ### 🙏 Credits - Original Author: **BubbaQ** - Prior Maintainer: **dlandon** - Fork Maintainer: **Uleepera** --- ### 📝 Notes This fork is intended primarily for archival and diagnostic use. Further development may continue depending on user interest or compatibility requests.

Hi, I have this setup for now. Trying to figure out how to create a topic in plugin support so I can submit. https://raw.githubusercontent.com/Uleepera/unraid-open-files-fork/main/open.files.plg Tested on 6.12.14. Description and icon are jacked at the moment, but everything appears functional.

Hi, I have forked the open files plugin that recently vanished and i'm trying to add it but I do not seem to have the ability to create a new topic? Do I need approval or to do something for this ability?

Can you recommend a good read on containers for Unraid? I'm trying to put this back up but I'm having a bear of a time getting the PLG file to work for some reason.

This still doesn't seem to be a resolution. I've tried 3 different locations both with the folders existing and without and I keep receiving the same error. [28.05.2024 14:46:19][❌][Main] Destination is unavailable or not writeable!

Have not had a chance to look at this yet. I will, my temp fix was to setup a VM and run everything thru a slim Ubuntu install which has worked but isn't optimal.

I read a post elsewhere of someone looking to modify parts of that file who said unRAIDs docker behaves abnormally if you add the file to the normal directory.