Objective
To troubleshoot and resolve the "archiveType unknown" error that appears in the Automox Events Log when applying software updates for FileZilla.
Problem / Symptoms
During a scheduled or manual patch deployment for FileZilla, the update fails, and the following error message is recorded in the Automox console Events Log:
Plaintext
archiveType unknownRoot Cause
The "archiveType unknown" error occurs when the Automox Agent is unable to properly download, extract, or parse the FileZilla installation payload. Common causes include:
Incomplete or Corrupted Downloads: Network security tools, SSL inspection, or strict firewall rules intercepting or modifying the payload download.
Directory Permission Restrictions: Local file system restrictions preventing the Automox Agent from creating or writing to its temporary working directory.
Security Software Interference: Endpoint Detection and Response (EDR), Next-Gen Antivirus (NGAV), or Secure Web Gateways (such as Netskope or Zscaler) blocking or quarantining the downloaded installer binary.
Resolution Steps
1. Ensure Allowlisting Rules Are Configured:
Verify that all required Automox domains, IPs, and binary download paths are allowed through your network firewall and web filter.
Refer to [Agent Firewall Allowlisting Rules](Agent Firewall Allowlisting Rules) for exact specifications.
2. Verify Local Working Directory Access:
Ensure the Automox Agent process has full read/write permissions to its working directory on the endpoint:
-
Windows:
C:\ProgramData\amagent\ -
macOS:
/Library/Application Support/Automox/
If local security policies restrict folder creation or script execution within these directories, update permissions accordingly.
3. Check for Security & SSL Inspection Conflicts:
Review local security software logs (e.g., Netskope, CrowdStrike, Defender for Endpoint) to check if the FileZilla payload download was flagged or intercepted.
- Temporarily disable or configure exclusions for Automox Agent binaries and temporary folders in your security software.
- Ensure SSL/TLS inspection bypasses Automox update domain URLs to avoid payload payload modification.
4. Review Agent Logs for Payload Details:
Inspect local agent logs for specific download or extraction failures:
-
Windows:
C:\ProgramData\amagent\amagent.log -
macOS / Linux:
/var/log/automox/amagent.log
Search the log files for references to FileZilla or archiveType unknown to pinpoint the exact failure point.
Escalation Requirements
If the issue persists after completing the resolution steps, submit a ticket to Automox Support with the following diagnostic details:
Affected Patch Policy Name and Device Names.
Screenshots of the error in the Activity/Events Log.
Attached local agent log files (
amagent.log).