Some company networks block or interrupt the addresses Hive uses for files. When this happens, people see messages such as Your network may be blocking Hive files, PDF could not be loaded or We weren't able to upload your files. Files and proofs then do not open or upload, even though the rest of Hive works.
Common causes are web filters and security tools (for example Microsoft Defender), proxies that inspect or cut off downloads, VPNs and firewalls.
Domains to allow
Ask your IT team to allow these domains, including all their subdomains:
*.hive.com(the Hive app, sign-in and real-time updates)*.hiveusercontent.com, includingdrive.hiveusercontent.com(opening and downloading files and proofs)hv-hive-drive.s3-accelerate.amazonaws.com(uploading files and proofs)cdn.jsdelivr.net(components the proof viewer loads)
Also make sure your network allows:
Secure WebSocket connections (
wss://) to*.hive.comLarge file downloads and partial (range) requests, which the proof viewer uses for big PDFs and videos
Hive's TLS certificates, so the connection is not decrypted and re-encrypted by an inspection tool that breaks it
Check that it works
Open a proof or file attachment in Hive.
Upload a small file to an action.
If either still fails, note the exact message and the time, then contact us at help@hive.com with the name of your security tool or proxy.
This article is a starting point. We will add more detail for specific security tools.
