Given that these control panels basically run the main website, I would have thought you’d test these releases much better than this. You’ve basically destroyed everything to the point that it needs a new install—and even that’s broken!
What’s the ETA on 1.9.2 to fix some of the problems with 1.9.1 listed here and on GitHub?
I’m honestly surprised that after 24 hours, there’s still no main fix released. Leaving installation and update issues unresolved for this long doesn’t reflect well on the script, especially when these problems were introduced in the latest update. If these issues aren’t addressed properly, it could impact the script’s reliability and reputation.
Additionally, your website is also experiencing issues. I’m not entirely sure who manages the repository or the site, but I’d like to ask again—what’s the ETA for a release that will fix the problems caused by 1.9.1? These issues are affecting both the control panel and new installations, so a timely fix would be greatly appreciated.
Well, if proper testing had been done in the first place, we probably wouldn’t be in this situation now. I’m not trying to be harsh—I understand it’s an open-source script and appreciate the effort that goes into it. However, leaving these issues unresolved for more than two days is a bit of a mess.
I have donated to the project, but at this point, I guess you get what you pay for. Hopefully, a fix is on the way soon.
Is installation script also broken?
Because this website alone can’t switch to dark mode, can’t click “install” link from home page, can’t copy the installer script, can’t configure as usual for what software I want to install.
Please let me know the payment id and I’ll refund.
We hardly work to fix the issues and provide new debs this night. We had two versions released, an alpha and a beta. Still we didnt have enough testing base, so maybe keep eyes open next time and help testing. thank you.
There’s no need for that—it was done a few months back, and it’s still a great project. However, you’ve released a broken product, and I think you might want to double-check your reply—unless you were being condescending with “We hardly work to fix the issues and provide new debs this night.”?!
Also, I haven’t seen any calls for testers or real engagement with the issues beyond being defensive.
Honestly, not really time for a discussion. Basicly a “product” is something you sell, we do not sell it. The beta test were published with sticky header threads in the forum. So either take your dono back if you want to use it as “argument” or help next time with testing and/or developing.
I understand that this isn’t the time for a long discussion, but the fact remains that a broken update was pushed out, and users are now dealing with the consequences. Whether or not it’s a “product” in the commercial sense, it’s still software that people rely on, and a certain level of responsibility comes with that.
I wasn’t using my donation as an argument—just pointing out that I’ve supported the project and expected a more stable release. I appreciate that beta tests were posted in the forums, but not everyone sees those threads, and it doesn’t change the fact that the update introduced major issues.
Instead of getting defensive, maybe take the feedback on board and improve the release process. I’d be happy to help test in the future, but that doesn’t change the need for a proper fix now.
It appears this boils down to one small typo (the extra ‘w’) in www.conf. While I am concerned with delivery time for 1.9.2 to address this simple issue; HestiaCP has had calls for testers. If you are following the forums or development; the call for testing has always been here. If you’re new to FOSS; testing is always a top, top, top priority. Especially if you are providing HesitaCP as a SaaS. For the sake of your own end clients; invest in testing (perhaps even above your own personal donations). Turn off automatic updates (HestiaCP has provided a simple and easy way to do this); and do testing before upgrading your end users.
Just a suggestion as a seasoned FOSS developer/contributor that wraps projects into ‘products’. The more folks that do this, the better the project becomes.
Beside “its not only a small typo”, there are other issues which needed to fix. A release will follow within the next few hours - as soon as packages are built and signed.