We recently discovered a serious bug in v7.0's handling of system configuration restores. A combination of system parameters can cause a restore to fail completely and disable a box. The only way to recover the box in this state is to reinstall from source media.
At this time we are recommending that users try to avoid restoring in version 7.0.
We will release a fully-patched version ("7.01") of Untangle ASAP (likely next week). We cannot set a final release date because we are still in the early stages of our Quality Assurance Process. But rest assured that we have been working on addressing these issues since 7.0's release.
We'd also like to take this moment to apologize to all of our Untangle users out there (over 20,000 installed instances now) both new and old. This release did not go as we hoped or expected. As a result, we've spent many hours reviewing and revising our release processes to ensure that something like this doesn't happen again.
We appreciate the frustration that this has caused many of you and your end-users. Please know that we do set a higher bar for ourselves than this, we just failed to reach it this time.
Included in the 7.01 release are the following fixes:
- Correction of various data throughput calculations on Reports
- Removal of erroneous KuGoo and Xunalei protocol signatures
- Additional error handling in reports server module to add robustness
- Support for IE8 on Config->Email module
- Correct configuration restore from backups