> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zappl.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

> Solutions to the most frequently encountered Zappl issues.

## Frequently Encountered Issues

Below are some of the most common issues encountered when using Zappl, along with an explanation of each and how to resolve them.

<AccordionGroup>
  <Accordion title="The install Zappl script fails to install Zappl">
    #### Symptom

    `Error: The Zappl deployment failed because the installer script is inaccessible. Please check the Zappl network requirements and try again.`

    #### Explanation

    The script was blocked when attempting to download the Zappl installer components from `zappl.co`.

    #### Remediation

    Verify that the network connection is stable and that the Zappl [Network Requirements](/about/requirements) have been met. Specifically, this requires outbound network access using port `443` (HTTPS) to `zappl.co`.<br />If the issue persists, the service could be experiencing a temporary outage.
  </Accordion>

  <Accordion title="App installation failure | Not enough disk space">
    #### Symptom

    `Error: Not enough disk space available to download and install the $appName update.`

    #### Explanation

    The app installer size is greater than the available disk space on the computer, preventing it from being downloaded.

    #### Remediation

    Free up disk space on the computer. The Zappl log displays how much space is required for the particular update/install, however it is advisable to free up as much space as possible to prevent further installs/updates from failing.
  </Accordion>

  <Accordion title="App installation failure | Incompatible OS">
    #### Symptom

    `Error: $appName is not compatible with this macOS version.`

    #### Explanation

    The installed version of macOS does not meet the macOS requirements for the app.

    #### Remediation

    Review the Zappl log to see the macOS requirement for the app.<br />If the installed macOS version is too far behind, upgrade the computer to the supported macOS version.<br />If the app can only be installed on older versions of macOS, limit installs of the app to computers which meet the required macOS criteria.
  </Accordion>

  <Accordion title="App installation failure | Could not download app">
    #### Symptom

    `Error: The $appName installer could not be downloaded.`

    #### Explanation

    Zappl could not download the installer for the app in question.

    #### Remediation

    Verify that full network access is permitted to the software vendor’s public download URLs and try again.<br />If the issue persists, the vendor may be experiencing a temporary outage.
  </Accordion>

  <Accordion title="App installation failure | Could not mount disk image">
    #### Symptom

    `Error: Could not mount disk image for $appName.`

    #### Explanation

    The disk image containing the software was successfully downloaded, but couldn’t be mounted.

    #### Remediation

    Remove any disk image restrictions. Disk images can be blocked using MDM configuration profiles and other third party security tools. Blocking disk images will cause any apps with .dmg installers to fail, therefore lifting these restrictions will resolve this issue.<br />If no restrictions are in place, the downloaded disk image may be damaged. In this case, retry the install/update and if the issue persists please [contact support](mailto:support@dare.tech).
  </Accordion>

  <Accordion title="Portal | Unable to send reports to email addresses">
    #### Symptom

    `The email address is not associated with an existing Zappl user. Please create a new user and try again.`

    #### Explanation

    For extra security, only existing users in the Zappl portal can receive scheduled email reports. If you try to schedule an email report for an email address that is not linked to a user in the Zappl portal, this error will be seen.

    #### Remediation

    [Create a new user](/portal/accounts#creating-user-accounts) in the Zappl portal using the desired email address for the scheduled report, then try again.
  </Accordion>

  <Accordion title="Microsoft Defender | Version has not changed since the update attempt">
    #### Symptom

    `Error: The Microsoft Defender version has not changed since the update attempt. Version installed: 101.25062.0005`

    #### Explanation

    In version 2506 (101.25062.0005) of Microsoft Defender, a bug caused tamper protection to prevent any future updates by any means (even via Microsoft AutoUpdate).

    #### Remediation

    [Follow Microsoft's guide](https://github.com/microsoft/mdatp-xplat/tree/master/macos/upgrade_from_2506_helper) to add a tamper protection exclusion for Microsoft's update helper, then run the helper PKG. Additionally, it is advised to create a second exclusion for Zappl in the same profile using "JTYACQP7Y5" as the team ID, and "com.dare.zappl" as the signing ID to ensure Zappl is excluded from tamper protection for future updates.
  </Accordion>
</AccordionGroup>