Resolve FileWave Kiosk SSL and Manifest Validation Errors (15.3+)

What
FileWave Kiosk installation can fail on macOS or Windows with a manifest validation error followed by an SSL error. The example below was first documented with Kiosk 15.3.1.
When/Why
This usually means the device cannot reach or trust the Kiosk package host. Common causes include a content filter that classifies the host as unknown, a proxy or firewall block, or SSL inspection that changes the certificate chain.
"InstallApplication	command error		2024-04-22T07:36:38	2024-04-22T07:36:38				Could not validate manifest..An SSL error has occurred and a secure connection to the server cannot be made.	com.filewave.ios.app.kiosk2	"
How
Check the network path used by the affected device:
Check the proxy, firewall, and content filter: Confirm that they allow the Kiosk package host and do not replace its certificate with an untrusted chain.
Allow the required URLs: Add the following entries to the appropriate allowlist:
https://fw-kiosk-v2-ipas.filewave.cloud/
*.filewave.cloud
The exact rule depends on your network security product. Apply the change to the same network path used by the affected devices.
Retry the installation: After the network rule is active, send the installation again and check the device command history.
# Example command to verify if the URL is accessible from your network
curl -Iv https://fw-kiosk-v2-ipas.filewave.cloud/
Run the command from the same network path as an affected device when possible. If the host is reachable but certificate validation still fails, inspect SSL/TLS interception and the device's trusted certificate chain.
Related Links
Default TCP and UDP Port Usage
Digging Deeper
The combined log message points to a network or trust failure while the device validates the Kiosk manifest. Fix reachability and certificate trust first, then retry the Kiosk command.