Hi Ludwig,
Thanks for the report!
The shown 2.6.7 version is just a wrong label. After the interrupted self-update, HTProtect safely rolled back to 2.6.6 – the file operations were fine. Only the version number in Joomla’s (database) list stayed at 2.6.7. This will fix itself with 2.6.8 (or immediately if you reinstall HTProtect once).
The rollback was most likely a false alarm. HTProtect checks right after the update if the site responds normally – so far with just one measurement at the most sensitive moment. A brief hiccup there (slow response, momentary SSL/connection error) was mistakenly / too quickly seen as a failure. For me, 98% of the 2.6.7 updates went through perfectly.
Starting with 2.6.8 it’s way more robust:
- Checked multiple times instead of once – a single hiccup won’t trigger a rollback anymore; a real failure (error page/500) is still reliably caught.
- SSL/connection errors and timeouts are considered “not measurable,” not “site broken” – those hoster/network glitches won’t cause rollbacks anymore.
Cheers
Pascal
