IP addresses, ports and firewalls
Two lists. What an agent on your network needs to reach, and the addresses Caryvane itself connects from — the ones to allow in a bucket policy, a conditional-access rule, a WordPress security plugin or a webhook receiver. Use the hostnames wherever your firewall takes them; the numbers are here for the kit that cannot.
What an agent needs outbound #
TCP 443 to console.caryvane.com. That is the whole rule. The agent uses it to check in, collect its instructions, report runs, send its logs and upload the backup index — and to fetch its own updates, which come from the same host under /downloads/agent/.
No inbound rule. Nothing in Caryvane connects to your machines: the agent makes every connection itself, outbound. You do not need a port forward, a static address or a VPN for it.
Plus whatever the job itself reaches. A backup that writes to Amazon S3 needs the S3 endpoint; a Microsoft 365 job needs login.microsoftonline.com and graph.microsoft.com; a Google job needs www.googleapis.com. Those are the provider's addresses, not ours, and they are the same ones any other software using that provider needs.
Port 80 is not needed. If a proxy inspects TLS by re-signing it, the machine must trust that proxy's certificate chain or the host must be exempt from inspection — otherwise check-in fails with a certificate error. To prove the path from a machine: curl -sI https://console.caryvane.com/healthz.
Caryvane's addresses #
| What | Hostnames | IPv4 | IPv6 |
|---|---|---|---|
| Console, API, agent check-in and updates, web drive, document editor, this help site and the website | console.caryvane.comdrive.caryvane.comeditor.caryvane.comhelp.caryvane.comwww.caryvane.com | 77.95.34.54 | 2a02:5300:6:1::54 |
| Caryvane Cloud Agent (United Kingdom) — the jobs you choose to run in our cloud instead of on your own hardware | — | 77.95.34.13 | 2a02:5300:6:1:be24:11ff:fec9:42f1 |
Every Caryvane system sits inside 77.95.34.0/26 and 2a02:5300:6:1::/64. The IPv4 range is registered to Centurion Computers, who develop Caryvane. If your firewall would rather have two ranges than a list of hosts, allow those two and you are covered for anything we add later.
Our hosts are dual-stack. Where the far end publishes an AAAA record, the connection may well come from the IPv6 address rather than the IPv4 one. Allow both, or block IPv6 outbound at the far end so it cannot be chosen.
Email is not sent from these addresses. Notification email leaves through Microsoft 365, so allow the sending domain rather than an address. Our record is v=spf1 include:spf.protection.outlook.com -all, and caryvane.com publishes DMARC.
Pre-release testing runs on a separate host at 77.95.34.48 and 2a02:5300:6:1::48. It only matters if you have agreed with us to run pre-release agents.
Which address a connection comes from #
It follows where the work runs, which for most jobs is your choice in the wizard. Get this wrong and an allowlist either blocks the backup or does nothing at all.
| Work | Connects from |
|---|---|
| Any job set to run on one of your agents — files, Hyper-V, SQL Server, Active Directory, Microsoft 365, Google Workspace, cloud-to-cloud, archiving | That machine's own public address, not ours. An allowlist at the far end needs your address. |
| The same job set to Caryvane Cloud Agent | The Cloud Agent address above. |
| Xero, Shopify and HighLevel backup | The Cloud Agent address. These never run on your hardware. |
| WordPress backup | The host you chose for the job — an agent of yours, or the Cloud Agent. Only an agent can reach a site on a private network; the Cloud Agent will not connect to a private address. |
| Test and browse on a storage target, and Check the connection on a WordPress site | The console address. These run on our server, whichever agent the job uses. |
| Webhooks Caryvane sends you | The console address. |
So a bucket policy that allows only the Cloud Agent will block the console's Test button, and the target will show as failing even though the backups themselves are fine. Allow both.
Where you might need to allow them #
- Amazon S3, Wasabi and other S3-compatible storage — a bucket policy with an
aws:SourceIpcondition. Include the console address as well as whichever host runs the job, or Test and browsing stop working. - Azure Blob — the storage account's firewall, under Selected networks.
- Microsoft 365 and Entra ID — only if you restrict sign-in by location. Add the addresses as a named location, or exclude the Caryvane app from the location policy. Nothing is needed when the job runs on an agent inside a network the policy already trusts.
- Google Workspace — context-aware access levels, if you use them.
- WordPress — a security plugin or edge firewall (Wordfence, Cloudflare and the like) will block the plugin's traffic. Allow the host running the job, plus the console address for the connection check. See WordPress backup.
- SFTP, FTP, SMB and local folders — always reached by an agent, so allow that machine. The Cloud Agent cannot be used for them.
- Your webhook receiver — webhooks arrive from the console address, but check the signature rather than trusting the address: every webhook is signed. See Notifications and webhooks.
When these change #
This page is the list — if an address changes, it changes here, and we tell account holders by email before a change that would break an allowlist.
Wherever your equipment accepts a hostname, use the hostname. Then a move on our side costs you nothing, and these numbers are only ever a fallback for firewalls that cannot resolve one.