Imaging Issue After Upgrading FileWave and Using Self-Signed SSL Certificate

What

After upgrading FileWave Server, IVS, and clients, imaging may fail when the environment uses a self-signed SSL certificate.

When/Why

Use this workaround when IVS imaging fails after an upgrade and the environment does not use a root-trusted SSL certificate. Add the check to your IVS upgrade process for self-signed certificate deployments.

How

1. Access the IVS via SSH or locally:
   • Connect to the IVS by SSH or local console. Use sudo -s so the following file edit runs as root.
2. Edit the dnsmasq.lua file:
   • Use your preferred command-line editor, such as vi or nano, to edit /imaging/scripts/bin/dnsmasq.lua:
     • vi /imaging/scripts/bin/dnsmasq.lua
     • nano /imaging/scripts/bin/dnsmasq.lua

1. Navigate to line 128:
   • Navigate to line 128.
     
2. Switch to insert mode:
   • In vi, press i to switch to insert mode. In nano, move the cursor to the line and edit directly.
3. Add the following line:
   • req.tls = false
4. Save and exit vi or nano:
   • Press the Esc key to exit insert mode.
   • In vi, type :wq and press Enter to save and exit. In nano, press Ctrl+X and save the file when prompted.
5. Verify functionality:
   • Test imaging again after saving the file.

Related Content

• Self-signed SSL Certificates
• Network Imaging / IVS