All Activity
- Past hour
-
Rafael Rutkowicz joined the community
-
Calling all multilingual HexOS users! Help us translate HexOS
trolle replied to jonp's topic in Announcements
Swedish, Native -
Kovence changed their profile photo
-
Calling all multilingual HexOS users! Help us translate HexOS
magor34 replied to jonp's topic in Announcements
Swedish, native. -
Calling all multilingual HexOS users! Help us translate HexOS
andredelange replied to jonp's topic in Announcements
Norwegian (bokmål) native -
Calling all multilingual HexOS users! Help us translate HexOS
Kovence replied to jonp's topic in Announcements
Norwegian (bokmål) Native -
Calling all multilingual HexOS users! Help us translate HexOS
Rex replied to jonp's topic in Announcements
Dutch Native -
Calling all multilingual HexOS users! Help us translate HexOS
SeniorSalty replied to jonp's topic in Announcements
German Native -
Calling all multilingual HexOS users! Help us translate HexOS
Nuzzas Katla replied to jonp's topic in Announcements
I'd like to help with Czech, and I'm a native Czech speaker. -
Calling all multilingual HexOS users! Help us translate HexOS
renesdk replied to jonp's topic in Announcements
Danish Native Dane -
jonp started following Calling all multilingual HexOS users! Help us translate HexOS
-
One of the things we hear often from the community is some version of: "I'd love to get my family/friends/parents onto HexOS, but everything is in English." We're fixing that. A translation system is coming to HexOS soon, and when it lands we want to launch with more than just English...which is where you come in. What we're looking for Community members who speak a language other than English and are willing to help translate the HexOS interface. You don't need to be a professional translator, and you don't need to be technical. If you use HexOS and you're fluent in another language, you're exactly who we're hoping to hear from. The goal is to make self-hosting approachable for people everywhere, not just for English speakers. Good translations are a big part of that, and the people who actually use the product tend to do a far better job of it than a machine. What it will involve We're still finalizing the details of the system itself, but expect something straightforward: a list of phrases from the HexOS interface that you translate into your language, at your own pace, with no fixed commitment or deadline. We'll share full instructions with everyone who signs up once we're ready to roll it out. How to volunteer Just reply to this post with: The language(s) you'd like to help with Optionally, your region or dialect if it matters (e.g. Brazilian vs. European Portuguese) That's it. We'll follow up here and reach out directly as we get closer to launch. Thank you in advance! This community continues to make HexOS better than we could on our own.
-
schmism joined the community
- Today
-
Yevhen Tsaplai joined the community
-
Here I am a few months later and seems the dream is starting to come true. I was getting pissed off at Plex and set up jellyfin in 3 minutes and had it working all from my phone on my recliner with my wife in my lap.
-
Gaurang Gautam joined the community
- Yesterday
-
Franks Charley started following Announcements
-
Franks Charley joined the community
-
s0lidworks joined the community
-
Jake Weaver joined the community
- Last week
-
Henry Varona joined the community
-
Miyana Ctheatham joined the community
-
To start, Docker is behaving correctly. But in HexOS, I'm seeing that the configured base 172.17.0.0/12 is technically invalid as a /12 network boundary, which is being normalized to 172.16.0.0/12. This results in automatic allocation of 172.16.x.0/24 networks. If the intention is to allocate only from 172.17.x.x, the base should be changed to 172.17.0.0/16. Practically speaking, when a user deploys apps, they typically appear to end up on new Docker bridge networks, which can quickly create IP conflicts for the few users out there using 172.16.x.x/16 networks. I noticed this after the TrueNAS login page was showing up unexpectedly for one of my unrelated endpoints. I'd suggest surfacing some configuration parameters somewhere in the UI, namely the Docker network pool config. As a more immediate fix: To reconfigure my HexOS deployment to use the 172.17.0.0/16 network ranges instead, I ran: root@HexOS[~]# midclt call docker.update '{ "address_pools": [ { "base": "172.17.0.0/16", "size": 24 }, { "base": "fdd0::/48", "size": 64 } ] }'
-
Show all drives, not only pools and unused drives
mill3000 replied to Jamespigeon's topic in Roadmap & Feature Requests
We'll put in on a list for consideration. Thanks for submitting your request. -
Arvind Sekar joined the community
-
new app curations read more about it here https://docs.hexos.com/en/release-notes/command-deck/2026-07-19
-
Quirky Kitsune started following Place Certain Apps Behind VPN
-
What would this app do? For the phone or computer?
-
I remember when HexOS first came out it was mentioned that an iOS app would be developed. Is that still the plan?
-
Show all drives, not only pools and unused drives
Jamespigeon replied to Jamespigeon's topic in Roadmap & Feature Requests
Also costum pool names please! I cant remember which pool is for what with these names. -
I am having the same issue, I have Windows and Linux. Unable to access files on the server from both operating systems. The HexOS Command Deck and TrueNAS webUI works fine. I restarted the router, restarted the server, and made sure the server was on a static IP. Linux has always worked fine, Windows I previously did the gpedit fix (Digitally sign communications ) and (Enable insecure guest logons ). I reversed those options in Windows and still no luck on accessing files on the server.