Incidents and maintenance reported on status page for Ferron https://status.ferron.sh/ https://d1lppblt9t2x15.cloudfront.net/logos/de5e1e6824618bb631e597564ce8209d.png https://status.ferron.sh/ en https://status.ferron.sh/incident/1050572 Fri, 04 Sep 2026 11:54:00 -0000 https://status.ferron.sh/incident/1050572#45cd0e3e1ee0d83f151487c11578fa326e112191ec2c8bbb901a0e0f5e23b3ff Incident The Ferron 3 Docker image that `smtp-01.hosts.ferron.sh` relies on is now based on Ferron 3.0.0-rc.2, and we updated that and that fixed the incident as a whole. Thank you for your patience. https://status.ferron.sh/incident/1050572 Fri, 04 Sep 2026 11:26:00 -0000 https://status.ferron.sh/incident/1050572#a2597719ffffe3924f0bc077a40062bc98871598c51186cb92a5f6017f9a07fa Incident Internal build of Ferron 3.0.0-rc.2 codebase has been deployed into internal staging Docker image, resolving the incident in `web-01.hosts.ferron.sh`. `smtp-01.hosts.ferron.sh` is still affected, as it uses a public Ferron 3 Docker image, which still has the version with critical bug. https://status.ferron.sh/incident/1050572 Fri, 04 Sep 2026 11:24:00 -0000 https://status.ferron.sh/incident/1050572#cef1c48ceb43c05f751f8a7a4e61b3ae5ed9e14a68029fa3e8d249cd8ea16035 Incident The incident happened, because of a critical HTTP/2 bug in Ferron 3.0.0-rc.1. Emergency bugfix of Ferron 3.0.0-rc.2 is compiling.