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

What

This article addresses an issue encountered during the installation of the new FileWave Kiosk v.15.3.1installation can fail on macOS andor Windows devices.with Users may encounter SSL errors anda manifest validation failureserror thatfollowed preventby 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 frompackage installinghost. correctly.

Common

When/Why

causes

Theseinclude installation errors typically occur when upgrading to FileWave v.15.3.1 and are primarily due to conflicts with certaina content filters or proxy settingsfilter that blockclassifies orthe misclassify necessary URLs. This is particularly relevant for organizations using content filtering solutions like Lightspeed, which may categorize essential URLshost as unknown, thusa blockingproxy them.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

To resolve these installation issues, followCheck the stepsnetwork below:path used by the affected device:

1. Check Proxythe proxy, firewall, and Firewallcontent Settingsfilter:: EnsureConfirm that yourthey organization'sallow proxythe orKiosk firewallpackage settingshost areand do not blockingreplace accessits tocertificate FileWavewith URLs.an untrusted chain.

2. WhitelistAllow Necessarythe URLsrequired URLs:: Add the following URLsentries to the whitelistappropriate in your content filter or proxy settings:allowlist:

   • https://fw-kiosk-v2-ipas.filewave.cloud/
   • *.filewave.cloud

   ThisThe exact rule depends on your network security product. Apply the change allows devices to communicate securely with FileWave servers and access the necessarysame resourcesnetwork forpath installingused by the Kiosk.affected devices.

3. ReattemptRetry Installationthe installation:: After updatingthe yournetwork settings,rule reattemptis active, send the installation ofagain and check the FileWavedevice Kioskcommand on the affected devices.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 issuehost persists,is checkreachable your SSLbut certificate settingsvalidation still fails, inspect SSL/TLS interception and networkthe configurationdevice's fortrusted anycertificate discrepancies that might be interfering with secure connections.chain.

Related Links

• Default TCP and UDP Port Usage
  

Digging Deeper

The SSLcombined errorlog typicallymessage indicatespoints anto underlyinga issuenetwork withor trust failure while the securedevice connection setup betweenvalidates the clientKiosk devicemanifest. Fix reachability and FileWave servers. This can be caused by SSL certificate verification failures, misconfigured proxies, or stringent network security policies that incorrectly classify or block legitimate URLs required for FileWave operations. Adjusting content filtering policies or proxy settings often resolves these issues, but further investigation into SSL trust settingsfirst, maythen beretry requiredthe forKiosk complex network environments. command.