All Activity

Quick follow-up after looking into this further. I was able to reproduce and fix the similar scrolling issue on my own site. In my case it turned out to be genuine responsive-layout overflow rather than a stale browser scrollbar. At short landscape heights, the content was only a few pixels taller than the available viewport. Looking more closely at my Command Deck recording, I noticed something that may help narrow this one down too: near the end, the menu reflows and extends onto an additional row. That seems like it could be increasing the overall page height just enough to create the slight vertical scrolling. It might be worth checking scrollHeight vs clientHeight at these short landscape viewport heights and whether the menu wrapping is what pushes the document beyond the viewport. On my site I fixed the equivalent problem by slightly compacting the landscape-only layout so the content fit, while keeping normal scrolling as a fallback for genuinely shorter screens. After making that change, I confirmed the issue is completely gone on my phone. Obviously Command Deck may have a different underlying layout, but hopefully the menu reflow gives you a useful place to look.

Nice to see. Thanks guys. -- Orion

Absolutely. Sent via email!

Thanks for taking the time to write this. Can you add some photo so I can send it to the Devs?

I noticed Command Deck has a tiny amount of page scrolling even though the UI looks like it’s intended to be fixed to the viewport. I ran into almost exactly this on my own site. In my case an off-canvas drawer extended beyond the visible frame and was still contributing to root overflow. The fix was to make the page shell itself the positioned clipping boundary: .site-shell { position: relative; overflow: hidden; /* fallback */ overflow: clip; } Might be worth checking whether one of Command Deck’s translated/off-screen panels, drawers, decorative elements, etc. is extending the document bounds. It can produce only a few pixels of scroll and be surprisingly easy to miss.

Yeah, what complicates their side further is that their dependency (truenas apps) have skipped versions before too.

I cannot log into my Dashboard? Why is that?

Would you expect this to be at additional cost? Sounds like they would have management responsibility on their servers and require additional staff. If it is a cost, how much per month is it worth to you?

Yes, that is indeed the case. I'm more refering to the fact that HexOS does not account for this limitation, just happily upgrades from 32 to 34 and in the process bricks the installation. In fact, it doesn't even have a method of performing such a sequential update, I needed to go into TrueNAS Scale in order to do updates 1 major version at a time. The "can't skip major versions" of Nextcloud's update process should be well known by now, and the app is not marked experimental. HexOS's update process shouldn't allow an update skipping major versions to be performed at all.

I have also long thought this would be the killer feature for HexOS. The user requirement of having all these wonderful new curated apps available from an external network in a secure and convenient manner.

https://docs.hexos.com/release-notes/command-deck/2026-08-07 Pretty significant update and groundwork has been laid for buddy backups (coming soon)!

They finally added the feature (kinda)! It doesn't change the name in TrueNAS, but in HexOS you can change the name shown for a pool. Thank you very much. Go in Storage, select a Pool and you'll have the Rename button available.

Fantastic - thank you! Loving th thematic release of all 3 together. Do you have any plans to incorporate the Data Importer tool for Firefly? https://github.com/firefly-iii/data-importer

Danish Native Dane

Danish Native Dane

And it just came back up (local host at the moment). Swapping to Hosted it doesn't like.

I am having this issue as well. The Deck GUI was working great for the last few weeks and now I cannot get it to connect to my server. I am still able to log in through the truenas UI and everything is up and running, but the Deck continues to tell me it is not able to connect to my server. It partially connected one time (the apps section had tiles, but they never fully loaded), but then immediately lost connection. Anyone help is greatly appreciated!

Could be wrong, but I think you have to update through every major (first number change) version sequentially. Looks like you skipped 33. If people are updating regularly they may not have this issue.

That suggestion's Origin is coming from a similar string inside of Deck. I have just enabled Google Cloud Translate API that you ALL can access from the Automatic suggestions tab.

Actually, I am getting suggestions like these: Where the translation and the suggested change are identical, but it still looks like it is suggesting it.

Suggestions would be great. It was confusing to me seeing that the Automatic suggestions sections are empty (until there is a translation). I would be against filling automatic suggestions as "needs editing" translations, though.

One question for the group: Weblate can show machine translation suggestions alongside each string as you work (from services like DeepL or Google Translate). You'd see the suggestion and decide whether to use it, tweak it, or ignore it on a per-string basis. Would that be helpful, or do you prefer working from a blank slate? We'll go with whatever the majority prefers.

Botom line up front: Nextcloud is not listed as an experimental app anymore, so I would hope that it wouldn't be possible to break it by clicking update in the HexOS app overview. Slightly longer version: I was running nextcloud 32.0.0, app version 2.0.34. Hadden't updated it in a while, and HexOS showed the option to update to 34.0.2 (app version 2.3.50). However, nextcloud only supports upgrading 1 major version at a time. So after upgrading, the docker immages are trying to spin up, but keep repeating that the upgrade from 32.0.0 to 34.0.2 isn't supported, and failing. I'm having to rollback to a snapshot and ry to do this update another way, not requesting halp in doing so, but I would have hoped that it isn't possible to need to do a rollback after clicking update brings the app into a unrecoverable state.

Hello, we have a bunch of fixes coming for this very shortly. It's tied up with buddy backups which is why we haven't pushed it yet. Just know it's coming out very soon!

Dutch, Flemisch. Native