Skip to main content

NinjaOne Backup — Error 360: Cloud Communication Error

Audience: T1 / T2 Use when: Backup fails with "Error 360: Cloud communication error."

What This Error Means

Lockhart cannot reach NinjaOne's cloud storage backend, which is hosted on Amazon Web Services (AWS). The local NAS leg of the backup may have completed successfully — Error 360 specifically means the cloud upload leg failed.

Step 1 — Rule Out a One-Time Transient Issue

AWS and NinjaOne can have brief platform issues. Before investigating:

  1. Trigger a manual backup run
  2. Monitor the activity log for 5–10 minutes
  3. If it completes: the earlier failure was transient — document and monitor

If it fails again with 360: proceed to Step 2.

Step 2 — Test Cloud Endpoint Connectivity

# Test all NinjaOne / AWS backup endpoints from the affected device
$endpoints = @(
    "backup.ninjarmm.com",
    "app.ninjarmm.com",
    "s3.amazonaws.com",
    "s3.us-east-1.amazonaws.com",
    "s3.us-west-2.amazonaws.com"
)

$endpoints | ForEach-Object {
    $r = Test-NetConnection -ComputerName $_ -Port 443 -WarningAction SilentlyContinue
    [PSCustomObject]@{
        Host      = $_
        Reachable = $r.TcpTestSucceeded
        DNS_OK    = ($r.RemoteAddress -ne $null)
    }
} | Format-Table -AutoSize

If any endpoint shows Reachable: False — the UDM or a DNS/firewall issue is blocking the connection.

Step 3 — Check UDM Content Filtering

The most common recurring cause of Error 360 at DTC sites: DNSFilter or UDM content filtering blocking *.amazonaws.com.

  1. Log into UniFi → Settings → Traffic Management (or Firewall)
  2. Check for any rules blocking outbound HTTPS to Amazon or cloud storage categories
  3. If DNSFilter is active at the site: verify *.amazonaws.com and *.ninjarmm.com are not in a blocked category
# Test DNS resolution — if DNS is blocked, resolution will fail
Resolve-DnsName "backup.ninjarmm.com"
Resolve-DnsName "s3.amazonaws.com"
# If these return NXDOMAIN or timeout: DNS filtering is the issue

Step 4 — Restart Lockhart

If connectivity tests pass but Error 360 persists — Lockhart may have a hung cloud connection:

Get-Service | Where-Object {$_.DisplayName -like "*Lockhart*"} | Restart-Service -PassThru

Wait 2 minutes, then trigger a manual backup run.

Step 5 — Check for NinjaOne Platform Status

If multiple sites are experiencing Error 360 simultaneously: this may be a NinjaOne or AWS regional issue.

Check: https://status.ninjarmm.com

If there's a known incident: document in the ticket, monitor, no action needed on DTC's side.

Escalate to T2 If:

  • All connectivity tests pass, Lockhart restarted, but Error 360 persists
  • Error 360 is occurring at multiple unrelated sites simultaneously
  • UDM content filter changes don't resolve it
Back to top