HestiaCP 1.10.3 releases to patch FileGator regression and firewall rule corruption
Service release issued four days after a massive feature dump to restore the file manager and fix a firewall reordering bug.
HestiaCP 1.10.3 has landed, bringing a service release focused on squashing regressions introduced earlier this week. If you upgraded to the massive 1.10.0 release on August 13 and found your file manager suddenly threw HTTP 500 errors, the latest update is right on time.
The gap between 1.10.2 and 1.10.3 is short by design. 1.10.0 shipped with PHP 8.5 support, Debian 13 and Ubuntu 26.04 LTS compatibility, over 40 security hardening commits, and a bunch of new quick-install apps. Regressions are inevitable when you move that fast. 1.10.3 is the cleanup crew, and it arrives on August 17, 2026.
Fixing the FileGator breakage
The headline item is the FileGator file manager. User @douxxtech filed issue #5619 on August 15 after updating to 1.10.1, reporting that navigating folders still worked but opening any file returned an "unknown error" from the /fm/?r=/download endpoint.
The cause was a missing symfony/mime dependency. The DownloadController imports Symfony\Component\Mime\MimeTypes, but the FileGator composer.json only listed a subset of Symfony packages. Corrupting the file manager isn't great, especially when it's one of the core tools you rely on to manage your websites.
Core contributor Sahsanu landed PR #5616 to add symfony/mime as an explicit requirement. The PR also jumps FileGator's PHP target from 7.2.5 to 8.1, a significant upgrade for users running legacy configurations.
Even better, Sahsanu caught a bug in the upgrade script itself just a day later. PR #5622 fixes an ordering issue where the script referenced a version variable before it was sourced, which would have caused existing installations to silently skip the reinstall. A quick patch corrected the sequence, and the commit landed on August 16. The fix to the fix, effectively.
Firewall rules and DNS polish
The next fix addresses a firewall rule reorder bug. If you deleted rules in the UI and then used "move up" or "move down" to shuffle the remaining entries, duplicate entries would appear because the internal numbering in rules.conf wasn't re-sequentialized.
Duplicate iptables rules can lead to unintended port openings or blocked traffic, so this is a genuine config hygiene fix. Sahsanu added logic to bin/v-delete-firewall-rule that re-sorts and renumbers rules sequentially, using an atomic write via temp file plus mv for safety.
Jaap Marcus also tweaked the CSS for DNS records. Long TXT records and CNAME chains were overflowing the grid layout on narrower screens. The u-text-break utility class now forces breaks properly, restoring the expected layout.
The release notes mention routine locale updates as well. The diff shows 2,503 changes with 899 additions and 1,604 deletions, reflecting a net cleanup of obsolete references and typo fixes across the shell scripts.
A small team keeping the lights on
It's worth noting who's maintaining HestiaCP. The project has around 4.5k stars on GitHub, yet releases are authored almost exclusively by Jaap Marcus and Sahsanu.
The rapid turnaround is notable. The FileGator regression was reported on August 15 and fixed by the time 1.10.3 shipped on August 17. That's roughly a 48-hour window from user report to stable release, which beats most commercial support cycles.
Head here to grab HestiaCP 1.10.3 on GitHub. If you're running any version from 1.10.0 through 1.10.2, updating now prevents that FileGator loop and keeps your firewall rules tidy.
