To function properly and secure your devices, Prey requires uninterrupted communication with our servers. Sometimes, strict corporate firewalls, network proxies, or local antivirus software can block this connection, causing your device to appear as "Offline" in your panel. You’ll need to set exceptions on your software/hardware of choice.
Network Firewall and Proxy Allowlist
Prey requires outbound access through ports 80 and 443. Please add the following Fully Qualified Domain Names (FQDNs) to your network's allowed sites list to ensure stable communication:
| Protocol | Port | Allowed Domain / FQDN |
|---|---|---|
| HTTP / HTTPS | 80, 443 | solid.preyproject.com |
| HTTP / HTTPS | 80, 443 | panel.preyproject.com |
| HTTP / HTTPS | 80, 443 | control.preyproject.com |
| HTTP / HTTPS | 80, 443 | exceptions.preyproject.com |
| HTTP / HTTPS | 80, 443 | downloads.preyproject.com |
| HTTP / HTTPS | 80, 443 | preyproject.com |
| HTTP / HTTPS | 80, 443 | (https://www.googleapis.com) |
| HTTP / HTTPS | 80, 443 | prey.io |
Local Antivirus and Endpoint Security Allowlist
If you use local security suites (like Windows Defender, Bitdefender, Malwarebytes, etc.), you must exclude Prey's installation folders and executable files from active scanning and blocking.
Add the following paths to your software's exceptions list:
- Windows: Allow the entire
C:\Windows\Prey\directory. Additionally, ensure the specific executableC:\Windows\Prey\current\bin\node.exeis allowed to run and connect to the internet. - macOS: Allow the
/usr/local/lib/prey/directory.
Note: Once you have applied these rules to your firewall or antivirus, you may need to restart the device for the changes to take effect and force a new connection attempt.