I've been working on this project for the past couple of weeks, and I think I'm at the point where other people can start trying it out!

Unraid Community Apps

StaXX for Unraid

StaXX is in beta: the core is settled and in daily use, but expect the occasional rough edge, and read the changelog before pressing update. Find StaXX for Unraid OS and install it from your server wi

StaXX

Docker Compose stacks for Unraid, with a form instead of YAML. StaXX is a plugin for Unraid 7.2+ that manages your containers using standard Docker Compose stacks instead of Unraid's XML templates. Paste in a compose file from anywhere, and it just runs. If you would rather not touch YAML, StaXX reads the file and builds a settings form from it, so you can configure a container the same way you do today. Whatever you save is still a plain compose file that works unmodified anywhere else. I've been building in lots and lots of features with a lot of automation as well that automatically fills things in like file paths and will automatically connect the same values that are used in a multi-service stack or even across stacks! Honestly, I can't keep up with all the things that I've been shoving into this! I'm working on updating all of the documentation as well, but you can try it out and let me know what you think. I think it's pretty intuitive.

Key Features

• Runs standard compose files, unchanged

• Intelligently turns a compose file into a settings form

• Imports and converts your existing Unraid template containers

• Imports a Docker Hub image as a starting stack; just give it the URL

• Groups stacks into folders on one page (Replaces FolderView)

• Start, stop, restart, recreate, realtime logs, shell and file manager for each service

• Checks for image updates on an intelligent learning schedule

• Roll back to a previous image build or historical YAML version independently

• Pin an image to one exact build

• Keeps an edit history of each compose file

• Autostart with the server and chosen order

• Export a stack as a shareable bundle*

• Optionally integrates deeply within the Unraid UI

CA: https://ca.unraid.net/apps/staxx-0626nzk0azbrks

GitHub: https://github.com/quadcom/Staxx

Feedback and feature requests: https://staxxfb.quadcom.ca

Bug reports and ideas are welcome on the feedback board. Tell me what breaks.

UPDATE: 10-02-26

I've had my head down working on the 05.00 release, and this is a big one. Here's a preview of the new features I've added, along with numerous tweaks and bug fixes. I apologize if some of this reads a little weird. Yes, I'm using a lot of AI for this. It is helping me tremendously, especially when it comes to writing out documentation. Writing documentation, coming up with features, and doing all the Q&A is incredibly taxing. So, a little patience with what's written in the help files and these features that are below.

StaXX 00.05.00 is almost here

Merge stacks: turn a pile of apps into one stack

Lots of apps arrive from Community Applications as separate pieces: the app, its database, maybe a cache. Merge joins them into one stack, and it walks you through every step so nothing changes behind your back.

• Pick two or more stacks from the Add menu. Each one shows up as a card with its icon, image, ports and live CPU and memory.

• Name the new stack and choose its folder and icon.

• Read each original file side by side with the merged one. Every changed line is marked. Hover it to see why, then approve or decline it. You can't move on until every change has an answer.

• The .env settings files are joined too. Any extra files that clash are sorted out on a folder tree that shows where each file came from.

• Set start order, health checks, updates and notifications for the new stack in one place.

• Docker checks the merged file before anything is written. You'll see "Docker validated", or Docker's own message if something is wrong.

• Your data comes with it. Storage that Docker manages carries over by name, so a database keeps its data without copying a thing.

• Port clashes are found and settled, even a single port hiding inside another app's port range. Published ports stay open unless you say otherwise, and StaXX tells you if another stack connects to one.

• Apps that need to talk to each other are put on a shared network, and their addresses are rewired to point at each other. An app that runs through a VPN container keeps running through it.

• Your comments, notes and shared settings blocks travel with the files. A main file plus an override file is merged as the pair it is.

• Nothing is deleted. The original stacks are retired: greyed out and kept on disk, with a one-press Remove once you've checked the new stack works.

• It's built to be careful. Two merges at the same moment can't both go through, and a stack that depends on a file the wizard can't see is refused by name, with the fix spelled out.

The user guide has a full worked example: joining the three Tube Archivist apps into one stack, with a picture of every step.

Report a bug or ask for a feature from inside StaXX

Most apps send you off to GitHub or a forum thread when something goes wrong. StaXX has a feedback form built right in, on every screen.

• Press the speech-bubble button in the bottom right corner of any StaXX screen, the editor and Settings included.

• Choose Bug report, Feature request or Improvement. Each one lands in its own section of the StaXX feedback board.

• Sign in once with your Google or GitHub account. There's no new account or password to make, and StaXX remembers you after that. You can disconnect any time in Settings, Integrations.

• Give it a title, say what happened, and paste screenshots straight into the text with Ctrl+V.

• The form floats over the page. Drag it out of the way, or roll it up to the top of the screen while you take a screenshot.

• Each report includes your StaXX and Unraid versions and the screen you were on, so I don't have to ask. Nothing else about your server is sent.

• For bugs, you can attach the things that help me find the cause: the stack's compose file, what happened the last time it started or updated, recent container logs, page errors, the self-test, and a record of your last few imports.

• Passwords, keys, email addresses, network addresses and computer names are swapped out before anything leaves your server. You preview every file first and can hide anything else you want kept private.

• If a file holds a number that might be an address, StaXX marks it "Check this file" and waits for you to look before sending.

• Attached files are private to you and the StaXX team, and they're deleted after 90 days.

• Once it's sent, you see exactly what went out and get a link to your report on the board, where you can follow it.

• When an import fails, a Report this problem button opens a bug report with the details already attached.

Notifications that tell you what happened

• Update messages now show the old and new version, the size on disk, the first lines of the release notes, and a mark when the major version jumps.

• A failed update says why in plain words, like a download limit or a tag that no longer exists.

• New alerts when an app keeps restarting, fails its health check, or stops by itself.

• An alert if Docker itself stops answering for five minutes, and another when it's back.

• For each kind of message, choose straight away, in a daily or weekly summary, or off. No summary is sent on a day with nothing to report.

• Quiet hours hold messages back. Failures always come through.

• An optional StaXX email with app icons and colours, sent to the address in Unraid's notification settings. Phone alerts stay short: a title and one line.

• A weekly reminder of anything still pinned, so a pin never gets forgotten.

• Send a test message and see the result right away.

Import from other compose tools

• Coming from Dockge, Portainer, Arcane, Dockhand or Komodo? Import finds their stacks and copies them into StaXX, even files a tool keeps inside its own container.

• Have stacks with no containers yet? Point Look in a folder at them, or browse to the folder.

• More Unraid templates import cleanly now, including ones with settings named only by a number and ones that set the same variable twice.

Help fixing a broken compose file

• A file Docker refuses is still saved. Its row turns soft red with a wrench, and one click takes you to the problem.

• A floating help window shows Docker's message, what it means in plain English, how to fix it, and a link to Docker's docs. The bad line is marked in red.

• For one common mistake, Fix it for me shows the change, makes it when you agree, and Undo takes it back.

• When StaXX meets a Docker error it can't explain yet, it can send it in with names, paths and addresses removed, so an explanation gets written. New explanations arrive once a day. You can switch this off.

A StaXX tile on Unraid's Dashboard

• Arrange your stacks on a grid of up to 8 columns and group them into folders.

• Give a folder an icon from four icon sets, a built-in symbol, your own picture, or one that cycles through the stacks inside.

• Right-click to start, stop or restart. Click a stack for live CPU, memory and network graphs.

• Folders on the Stacks page can have icons too.

More control over updates

• Pin a service to the exact build it's running. Pinned services are skipped by update checks and bulk updates. To unpin, pick a tag from a list.

• Set update and notification choices per container from the editor or the right-click menu, or for many stacks at once with Select.

• Recreate on the row menus rebuilds containers from the file. The restart-pending chip can rebuild only the services that changed.

• Roll back works again, including for linuxserver apps like Plex.

• Check for updates counts through your images as it goes.

Storage clean-up

• Scan stored images shows a bar of how Docker's space is used: in use, kept for roll-backs, clutter and free. The list shows only real clutter, and the sizes count what removing it actually frees.

• Clear out what Unraid Docker and Compose Manager left behind, like old templates. StaXX keeps a copy you can put back.

• Damaged containers are flagged and can be cleared. If Docker won't let go of one, StaXX offers to restart Docker and try again, and warns you first.

• No more scheduled image removal. A notice tells you when clutter builds up, and you decide what goes.

• Removing a stack also clears roll-back images that nothing else needs.

Proxy and DNS built in

• Connect Nginx Proxy Manager and Pi-hole in Settings, Integrations.

• Add a domain, certificate, WebSockets and a Pi-hole entry to any app from the editor. StaXX shows what it will change, then does it when you press Apply.

• A small DNS mark on the stack list turns green when everything matches and red when it has drifted. Click it to fix.

A clearer stack list

• Status chips follow one colour scheme: green is working, grey is resting, blue is good to know, amber needs you, red is broken. A legend explains every mark.

• One Add button holds New stack, Apps, Import, New folder and Merge.

• Pick stacks with Select, and Start, Stop, Restart, Check and Update appear right below it.

• CPU now shows a share of the whole processor, from 0 to 100%, and each graph has its own colour.

• Apps with a health check get a gently breathing green chip. Apps that update themselves get a small green mark.

• StaXX tells you when it can't see the ports of apps on the server's own network. If one can't start because its port is taken, it names the port and what's using it.

Editor improvements

• Drop a picture or a picture link onto a service's icon to change it instantly. Each service keeps its own icon, and a stack shows them tiled together.

• Fold away any section of the editor. StaXX remembers what you folded.

• The Image box suggests tags: the usual choices first, then version numbers and images already on your server.

• Click a setting that uses an .env variable and its line lights up in the .env file.

• Download a container's whole log as a file from the Manage tab. The file manager has its own on/off switch.

Settings

• A tidier layout, with the self-test on its own tab. It runs when you open it and has a Copy button, ready to paste into a post here.

• A new About tab shows your StaXX version and which Docker Compose is running.

• The backup check now covers your whole StaXX folder, settings included.

• The copy kept on the flash drive is rewritten only when something really changed, so the flash gets written to less.

A rewritten user guide

The guide now reads as a step-by-step manual, with close-ups of the controls each page points at.

00.05.00 is in final testing and should land very soon. If you try it and something's off, the new feedback button is the fastest way to let me know.

Thanks to everyone who has been testing and sending in ideas.

Edited October 5Oct 5 by aglyons
05:00 progress announcement

CA Submission is in! Fingers crossed ;)

So the plugin has been on the Unraid CA for a little while now, and I see that there have been some people downloading it, so that's always cool to see.

https://ca.unraid.net/apps/staxx-0626nzk0azbrks

I would love to hear feedback from people: what they love, what they hate, and what they'd like to see different. Feedback is always great to hear.

While you can write stuff in this thread. I'll check it from time to time. If there is something very pressing, then by all means post a card up on my bug tracker/feature tracker that's dedicated to Staxx.

https://staxxfb.quadcom.ca/

I really hope this is a plugin that people find useful and really come to like.

Staxx came at the perfect time for me this week! I needed to roll out a new docker "stack" on my machine, and I finally decided to try and do it in compose to keep things cleaner. I happened to find Staxx in CA while I was considering the latest compose options, and after seeing the feature set, I decided to take it for a spin.

I have not completely migrated all my dockers over, but I have set up a new Staxx stack from a compose file, installed an app from CA into Staxx, and migrated an existing container over to Staxx. All went pretty well! After gaining a little bit of knowledge through experimentation and exploring the Staxx UI, I was able to find the features I was looking for and get a number of containers running and working as expected in my environment.

Overall, I am impressed with the abilities of the plugin. Since I'm not a regular compose user, I might not understand what Staxx may be missing that would be beneficial for doing complex compose setups, but for typical, everyday setups, I found it pretty easy to get comfortable with and use. Though, I found a couple bugs, and have a few suggestions which I will list below, I plan to continue to use this plugin for my docker needs in preparation for compose integration in Unraid 8. I hope the @limetech devs take note of this plugins functionality as they work on the next native implementation. This solution checks a lot of boxes!

Edited September 17Sep 17 by JesterEE

Feedback:

• It took me a while to notice the 'add file' buttons for the compose configuration. Now that I see it, it's obvious, but it took me forever to find it. Maybe it's just me, but if the '+' button were closer to the compose.yaml tab like it appears on modern web browser UIs, I think I would have found it faster.

• Dragging and dropping a stack onto a folder will yield an error "Only a ".staxx" bundle can be dropped here." I realize this is not the proper way to add a stack to a folder, but it is intuitive to perform this action since it looks like a file explorer, and it doesn't do what was expected.

Bugs:

• .env files do not display blank lines. Also causes navigation/display corruption in the editor.

• Staxx does not respect the Unraid lock sortable items UI element.

• Folder Collapse/Expand arrows always displays "Collapse" regardless of state

• Unable to return to split view after selecting Form/Compose view

Feature Requests (by desire level):

1. Dashboard docker widget integration (Similar to FolderView3)

2. Stack/Folder custom icons (Similar to FolderView3)

3. Notification/Automerge of upstream docker compose environment (YAML, env files, etc.) modifications

   • One of my biggest gripes with the current Unraid docker template system is that when a docker template is updated by the author, there is no way for a current user to easily merge the changes into the template deployed in Unraid. Staxx offers an infrastructure that could do this better while not compromising user modifications to the upstream configs.

Edited September 17Sep 17 by JesterEE

Hey @JesterEE , thanks for checking out the project. I hope this is all still relevant once UR8 is released, with them jumping into the compose situation as well.

I addressed your concerns, all except one as I can't seem to replicate the problem. Folder Collapse/Expand arrows. They change on my system, and I've reviewed the code there as well. SO I can't explain why you're seeing that.

In the future, submitting bugs or feature requests is best done on my board: https://staxxfb.quadcom.ca/. You can paste screenshots directly into posts, which seems difficult, if not impossible, on these boards. I'll be working on adding in-app bug reporting soon that will make the process even simpler.

Again, thanks for checking Staxx out. I also really appreciate the feedback and the review!

@JesterEE

I wanted to touch on the features you asked for.

1. Dashboard docker widget integration (Similar to FolderView3)

I can look into this. Can you describe what you would want to see there? I think shoving all your services would get the dashboard cluttered pretty quick. Pinning specific items might be useful. But could operational statistics, resource graphs stuff like that, is that something that would be a good addition?

2. Stack/Folder custom icons (Similar to FolderView3)

The main stack icon, as it stands right now, is a tiled view of the defined services. If you set the service icons as you like, the stack icon will reflect a tiled composite of them. For folders, I hadn't considered changing the folder icon itself, but I can add that to the possibilities list.

3. Notification/Automerge of an upstream docker compose environment (YAML, env files, etc.) modifications

4. One of my biggest gripes with the current Unraid docker template system is that when a docker template is updated by the author, there is no way for a current user to easily merge the changes into the template deployed in Unraid. Staxx offers and infrastructure that could do this better while not compromising user modifications to the upstream configs.

So StaXX does have automatic metadata and project example scanning along with automatic service icon pulling. It's by no means complete, as there's no defined standard. What it does is scan GitHub repos linked to the service, pull in the example compose file, and suggest items your current YAML is missing or items your YAML has that the examples don't. This covers new features that a repo might add to a project that require ENV vars or other accommodations in order to take advantage of. Another function is tracking when an image moves from one repository to another, such as when the source image used to be on Docker Hub but is now hosted under GHIO. It ensures it is the same author and doesn't just point you to some random image with the same name.

On 9/17/2026 at 3:00 PM, aglyons said:

Hey @JesterEE , thanks for checking out the project. I hope this is all still relevant once UR8 is released, with them jumping into the compose situation as well.

I addressed your concerns, all except one as I can't seem to replicate the problem. Folder Collapse/Expand arrows. They change on my system, and I've reviewed the code there as well. SO I can't explain why you're seeing that.

In the future, submitting bugs or feature requests is best done on my board: https://staxxfb.quadcom.ca/. You can paste screenshots directly into posts, which seems difficult, if not impossible, on these boards. I'll be working on adding in-app bug reporting soon that will make the process even simpler.

Again, thanks for checking Staxx out. I also really appreciate the feedback and the review!

Your welcome! It's really been nice updating my homelab with StaXX. IMHO docker compose is now necessary for deploying most docker services on a homelab. Gone are the days of spinning up a single container to handle a whole workload, and StaXX makes the transition from individual, disparate images to organized stacks bearable. I'm glad I found it when I did!

Thanks for hearing out my comments and feedback! I have already been using some of the features you implemented and I'm finding less "gotchas' as I use the tool. Originally I tried to use your dev board to submit my bugs and requests, but it asked me to create a login. Sorry to say, this was a dealbreaker for me using your submission system . I understand why this makes it easier for you as you work with your AI assistant to make the tool better, but for me as a user, it's just one more set of credentials I have to manage for a system I won't use more than a few times. I understand why you'd want/need a login mechanism for this service to keep the garbage out of your tracker, but to encourage user input, might I suggest a different means of verification like OpenID Connect. This might be overkill for your project, but it also may encourage others to contribute.

About the Collapse/Expand arrows, I still see it on my end, but I have been experiencing issues with the Docker page on my server updating dynamic events properly (e.g. refreshing after an update). I believe this may be due to the FolderView3 plugin, which is mostly pretty great, but can be somewhat wonky at times. Using the STaXX settings, I moved StaXX it to it's own page to hopefully remove any plugin conflicts with the default docker page, but I still see this issue. Take this as a grain of salt as this very well could be a me issue and I'm ok with that; it's extremely minor and does not affect the way StaXX works. See included screenshots of a simple folder with a single stack.

Thanks again for working on this and I will report back if I find anything else as I continue to migrate images and deploy new services.

On 9/17/2026 at 3:15 PM, aglyons said:

@JesterEE

I wanted to touch on the features you asked for.

1. Dashboard docker widget integration (Similar to FolderView3)

I can look into this. Can you describe what you would want to see there? I think shoving all your services would get the dashboard cluttered pretty quick. Pinning specific items might be useful. But could operational statistics, resource graphs stuff like that, is that something that would be a good addition?

2. Stack/Folder custom icons (Similar to FolderView3)

The main stack icon, as it stands right now, is a tiled view of the defined services. If you set the service icons as you like, the stack icon will reflect a tiled composite of them. For folders, I hadn't considered changing the folder icon itself, but I can add that to the possibilities list.

3. Notification/Automerge of an upstream docker compose environment (YAML, env files, etc.) modifications

4. One of my biggest gripes with the current Unraid docker template system is that when a docker template is updated by the author, there is no way for a current user to easily merge the changes into the template deployed in Unraid. Staxx offers and infrastructure that could do this better while not compromising user modifications to the upstream configs.

So StaXX does have automatic metadata and project example scanning along with automatic service icon pulling. It's by no means complete, as there's no defined standard. What it does is scan GitHub repos linked to the service, pull in the example compose file, and suggest items your current YAML is missing or items your YAML has that the examples don't. This covers new features that a repo might add to a project that require ENV vars or other accommodations in order to take advantage of. Another function is tracking when an image moves from one repository to another, such as when the source image used to be on Docker Hub but is now hosted under GHIO. It ensures it is the same author and doesn't just point you to some random image with the same name.

1. The ask here is a StaXX dashboard widget that replicates/overrides the docker widget's functionality with folder/stack layering. See the included image of a sample of my docker widget with the FolderView3 tweaks enabled on my server's dashboard. Note that there are "folders" for grouped services which are expandable/collapsible, and all the other non-grouped services are listed below it. Show started only vs show all remains intact, and the docker grouping I implemented in the plugin is preserved on the dashboard widget. I can control the running status, launch the WebUI, command prompt, log window, etc. right from the dashboard. Currently, I have FolderView3 working with StaXX to provide this functionality. For example, in the image I shared, the ddns-updater container is deployed in StaXX while Nginx Proxy Manager is deployed as a normal docker. Even though Unraid registers my ddns-updater container as managed by compose, it still lists it in the docker page and thus still applies the folder rules I set in FolderView3 to group it with my other Networking containers. I'd like to abandon all need for FolderView3 with a complete migration to StaXX and this it a hold-out feature for me. It is also why I requested adding custom stack/folder icons in (2).

2. One thing that FolderView3 can do that I really like is using 3rd party icons for folders; specifically hernandito's Animated "Docker-Folder" Icons for unRAID. Is it functional? No. Is it silly? Yes! But, we are simple creatures and it brings me joy to see nice animated images for my deployed services.

3. & 4. I was surprised to see many projects don't offer a source of truth docker compose YAML file indicating the many options available to the container. This was a little surprising for me coming from Unraid templates which, more or less, usually include a means for full configurability of the container from the source template. Now that I know this, StaXX is doing a good job at trying it's best to be smart, but the source maintainers aren't making it easy. This is yet another challenge the Unraid devs face as they embrace compose in the future. For StaXX, I think you're doing the best you can, and I can't think of a better way to do it so please disregard these requests. I hope a better solution emerges in the future, and if that happens, I think you already have the infrastructure in StaXX to embrace it.

I know I compared StaXX to FolderView3 a bunch, but I think StaXX gets to the real heart of the matter while FolderView3 just masks the inherent limitations of a non-compose based deployment in the Unraid GUI. I think StaXX is in a position to do it all better, but the lessons learned through the development of the many iterations of FolderView should not go to waste. If you are unfamiliar with FolderView and don't want to install it to see (I get it!), I suggest watching a few of AlienTech42's YouTube videos on the configuration of the plugin so you see what it can do and how StaXX can benefit.

Edited September 25Sep 25 by JesterEE

Hey @JesterEE, not sure if you saw the edit I made to the primary post about v05.00 release.

There are a lot of your 'wants' in there. Including SSO on the support boards. I also built the submission process directly into the UI, so you don't even have to leave the Unraid/StaXX UI. Oh, and a new Dashboard widget. I hope it fits the bill.

Edited October 4Oct 4 by aglyons

On 10/4/2026 at 2:15 PM, aglyons said:

Hey @JesterEE, not sure if you saw the edit I made to the primary post about v05.00 release.

There are a lot of your 'wants' in there. Including SSO on the support boards. I also built the submission process directly into the UI, so you don't even have to leave the Unraid/StaXX UI. Oh, and a new Dashboard widget. I hope it fits the bill.

Can't wait to give it a shot! I'm now 100% migrated over to StaXX and enjoying the flexibility it offers. So far, everything has been bulletproof! Thanks for your killer plugin!

I also added a few items to your tracker so I don't further contribute to the bloat on this thread for dev items. Thanks for implementing the OAuth!

Edited October 9Oct 9 by JesterEE

00.50.00 is out! Do let me know what you think.

Thx,

A

@JesterEE , any feedback on the dashboard widget? I was a folderview user in the past as well, although I never really used the dashboard part that much. I hope what I built out works for your use case.

I haven't had too much time to play in the lab the last couple weeks but I did get some time yesterday to work with StaXX a bit more. Since last I used the interface, I can tell there has been a significant amount of changes, both on the UI and under the hood. All the new notifications seem to work well with the core UI and the info being conveyed feels intuitive for the compose initiated. At this point I feel very comfortable navigating the UI and it feels purposeful and informative. I tend to use a combination of the template and the notepad editor depending on what I'm trying to do, and for small to medium sized compose files it works great. Once my stack starts to get a bit large (4-5 containers), the UI lag gets significant and the synchronization between template and text editor gets "touchy" where a short cursor move on the editor snaps the template interface. It's pretty hard to describe, but it's like a rubber banding effect that makes navigating difficult and further lags the page.

Lately my biggest gripe right now are the errors that get generated by breaking the syntax in the compose.yml file. The screen will spam with parsing errors in popup dialogs and it's hard to get control back to the interface. Outside of that, I think everything is coming together and I'm excited to see what you are looking at next. I'll log that but report as well as a few more feature requests that have come up since my last submissions.

As for the dashboard widget I like it! At first I didn't like that it didn't bring over my folders from StaXX for me, but then I realized I wanted to change some of the folder structures for my dashboard so that it's actually wound up being a little different than my StaXX UI. Maybe it would be good to default a stack to the folder that it was first assigned to in the StaXX UI but then allow the user to change the dashboard placement independently? Also, when I change the number of columns and rows to a smaller number than the default, the stack tiles got bigger to fit the space, but whenever the dashboard loads, it defaults to a four column grid until the code adjusts the size and snaps the stacks to the users grid specification. I'm nitpicking, but that snap is a little jarring. Could that page load the user selected grid size before loading the default grid to avoid the jumping widget?

@JesterEE Couple of questions.

try 00.05.02 which is just getting pushed out.

- which browser do you use: Firefox or Chrome

- How do you open Unraid with http:// or https://

I just discovered myself that Firefox, if you are not connecting to an SSL site it injects significant lag and browser freeze-ups and unresponsiveness. It was a pain in the ass to try and troubleshoot and figure out, but once I discovered that that is the case, when you flip over to an SSL connection, it's night and day difference, smooth, fast, responsive, no lag, So if you're using Firefox, can you try out Chrome? And also try the new release that's just getting pushed out.

Other issues addressed as well from some other users.

I've been using this plugin for a couple of weeks, and I'm loving it so far!

Just a couple of things:

-I have been trying to put my Immich containers in the ImmichBackup folder, but I can't seem to be able to do so. Dragging and dropping them into the folder (Which would make sense to me to do) only seems to give me the "Only .staxx files can be dragged and dropped". I checked the documentation for working with folders, and it seems to state that there should be an option to move stacks to a folder in the Stack Actions, which does not seem to be present for me.

I think for this specifically, I'd like to be able to drag and drop stacks into folders, or if that's not possible, let me select the stacks and give me an option at the top right to add them to a folder.

-I accidentally deleted the data store out of my appdata folder, and was able to recover it from the boot drive. However, all of the containers that had icons no longer do. Is there an easy way to recover those icons?

-Lastly, I'd love to be able to see my Container and LAN IPs and ports, as well as Volume Mappings at a glance, same as the Unraid Docker page. I think all of that info should be able to be hidden for folks who don't need to see all of that.

I am running Version 00.05.02. Thanks for all the great work!

Hey @febreeze

Thanks for checking out my project.

Sorry for the delay getting back to you here. I don't check this too often. I built-in a bug/feature report tool into the UI. The bubble at the bottom right will prompt you to log into my Bug tracker using either Google or GitHub. You'll then see a small form you can drag around the page, enter your comments and also minimize so you can grab a screen shot to paste into the form. It's the fastest, simplest and dependable way to get in touch with me about problems or feature requests.

To move stacks into a folder you have to unlock the UI with the Unraid padlock. Then you can right click on a stack and you'll see the move to folder options. The drag and drop is for a feature ice been planning for a bit but isn't released yet.

The IP and port details are present in the grid. Not sure why you could not see them.

Regarding the icons, you can go through one by one and no pick a new one by tapping the icon image space. But that could take some time. So I've put in a patch that will re-find a matching icon for the container when the current icon path is missing. I've also added in backing up the icons to the flash with the compose files. That should fix things up.

Keep the feedback coming.

On 10/27/2026 at 7:52 PM, aglyons said:

Hey @febreeze

Thanks for checking out my project.

Sorry for the delay getting back to you here. I don't check this too often. I built-in a bug/feature report tool into the UI. The bubble at the bottom right will prompt you to log into my Bug tracker using either Google or GitHub. You'll then see a small form you can drag around the page, enter your comments and also minimize so you can grab a screen shot to paste into the form. It's the fastest, simplest and dependable way to get in touch with me about problems or feature requests.

To move stacks into a folder you have to unlock the UI with the Unraid padlock. Then you can right click on a stack and you'll see the move to folder options. The drag and drop is for a feature ice been planning for a bit but isn't released yet.

The IP and port details are present in the grid. Not sure why you could not see them.

Regarding the icons, you can go through one by one and no pick a new one by tapping the icon image space. But that could take some time. So I've put in a patch that will re-find a matching icon for the container when the current icon path is missing. I've also added in backing up the icons to the flash with the compose files. That should fix things up.

Keep the feedback coming.

Hey thanks so much for getting back to me, and copy that on the feature report tool. I will use that for anything else in the future!

For the icons, I dug through the compose files and saw this:

    x-unraid:
      icon: ./.staxx/ddns-updater.png  # was https://raw.githubusercontent.com/DiamondPrecisionComputing/unraid-templates/master/templates/img/ddnsgopher.png

I simply removed the # was and everything before it and that seemed to do it. It's a little tedious but I don't have too many containers thankfully so it only took a couple minutes to do. I'd imagine your patch essentially automates this?