Import Old Configuration into New Version
Automatically Using Admin UI
In order to restore the configuration from old version of Web Safety into a new instance, navigate to UI / Dashboard / Tools / Restore, select the zip file created on the previous step, select appropriate checkboxes and click the Execute button as shown on the following screenshot.
After restore completes, click Save and Restart button in the top right corner and then re-enable HTTPS filtering and upload Root CA HTTPS decryption certificates from the zip file. It is recommended to do this as a separate step in order to correctly re-initialize Squid’s internal storage of SSL mimicked certificates.
You might also need to test Active Directory integration again and enable Kerberos/NTLM and Basic LDAP authentication schemes.
Manually Using Console
If automatic upgrade fails, upload the backup zip file to new proxy box to
/root/data folder, unpack it (so that
etc folder is direct subfolder of
/root/data) and run the following script.
#!/bin/bash set -e # check we are root if [[ $EUID -ne 0 ]]; then echo "This script must be run as root" 1>&2 exit 1 fi # import all data python /opt/websafety/var/console/upgrade.py --etc_dir=/root/data/etc --version=6.0 # now MANUALLY copy over other files from ./data if needed (html, key, der, pem) # and reset the owner just in case chown -R websafety:websafety /opt/websafety
Please adjust the
--version=5.2 argument if you are upgrading from on older version. Supported versions are 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 5.0, 5.1, 5.2 and 6.0. Not every item from older version may be upgraded.
After import is complete, manually copy the all files (except JSONs) from your data folder to the
/opt/websafety/etc, overwriting those that exist there. Again, do not forget to click Save and Restart from Admin UI.
In case of any errors during upgrade, you can send the zip with backup to firstname.lastname@example.org to reproduce and fix the issue. Please DO NOT include certiticates (*.pem)!!!