Zizuar

I'm seeing some command deck updates, but the last mention of the Q2 update was over a month ago when there were tests being done. Even one reply mentions shipping it the night of 6/26, but then I can't find a single further mention. 😞 Sadly I lost all faith in the HexOS team and moved on to new projects. Only when I see someone post something on YT or something have I been coming back to check and see if anything has been released or if they are even bothering to communicate (dev side.. not administrator. The admin tend be active, but that doesn't much help the project..). I made multiple posts pleading with the dev team to at least start dev-blogging or adopting an agile reporting cycle to keep the community invested. Sadly it appears things have been steadily declining as predicted. I wonder how many other community developers like myself gave up and decided to create the custom apps they wanted on another platform? Heck, from what I can tell we're halfway through Q3 and still waiting on the Q2 update to drop? I know how projects like this go, and not really surprised or down about the release delays. What makes me shake my head is the predictable damage done long term by ignoring voices from the community and not actively engaging with weekly or bi-weekly devlogs. Beating a dead horse here.. but a 5-minute single or double paragraph post on a bi-monthly cycle would have done so much to maintain goodwill if not hype and ecosystem investment. What do any of us know though? Not like some of us haven't managed larger enterprise development projects than this.. or won awards from global brands showcasing our builds on the TS NASDAQ tower. (yeah.. I sound petty and bitter right now, but mostly just because I was totally hyped and invested both in the vision and buying multiple licenses simply for support. I should know better by now how these things go though.) Okay okay.. I apologize for being a c*nt. I'll go back to the shadows and check in silently down the road to see how things go. (Gonna be watching for that redemption arc that's coming! {..hopefully})

😂 ..implemented..

3 different network storage machines? I hope at least one is totally off-site where you simply store backups. Data redundancy is important, but if they are all on the same network the entire set is vulnerable to malicious attacks. Only mention it because it sounds like a worst-case scenario you're planning for, and if so this needs to be a link in your chain.

If I had the time right now I would probably give a proxmox setup a fun go. Other than some virtual windows servers at the office that used to house our on-prem CRM I've never really played with virtual machines. Think it would be a fun change.. Just have wayyy too many projects I'm behind on atm. 😞

Out of curiosity then, what are you planning on using Hex for? Just simple network attached storage w/ raid failover availability? It almost sounds redundant with what you have running on the side there.

Are you running all of these docker container apps natively in the Ubuntu VM? I'm just curious if your Ubuntu VM and HexOS VM are separate side-by-side systems or if you were able to get the TrueNAS version of the VM to play nice in Hex? I'm assuming since you're running Prox it's the former rather than the latter. If so, do you have a plan to easily migrate all those apps if/when the time comes? I suppose that means rather than the native apps coming to Hex in the future you'll be spinning up Docker or a layered VM when that becomes an option.. Also.. if it will be a layered VM how do you intend to combat the resource negotiations and network hurdles that often comes with nesting virtual environments? Thanks.. sounds like you're off to a great start!

Glad you got it resolved. You should be able to change the IP address manually through Hex on the dashboard.. of course you would need to be able to access the server via deck in the first place to do it which was why I made the suggestion to revert everything to the old IP. Either way, sorry I wasn't able to be more helpful.

Not that this shouldn’t be something that Hex updates automatically on network changes or config updates, but another thing you can do is take the original IP and permanently assign it to your sever via your dhcp. This way also ensures that your modem/router doesn’t periodically assign the server an alternate ip as well.

Most non-professionals probably aren't familiar with High Availability.