Articles on: Lumen5 for Enterprise

Running Lumen5 on a restricted or corporate network

Some corporate networks (especially those behind a firewall, VPN, web proxy, or content filter) block parts of Lumen5. The most common symptom is uploads failing (images, videos, or documents won't go through) while the rest of the app works. This article lists what your network/IT team needs to allow.


Domains to allow

Allow HTTPS (port 443) to the following root domains and all their subdomains:

Domain

Used for

*.lumen5.com

The Lumen5 app, uploads, and supporting services

*.googleapis.com

File storage and uploads (Google Cloud Storage)

*.cloudflare.com

Content delivery and security

*.picdn.net

Stock photo and video library

*.stripe.com

Billing and payments

*.hubspot.com, *.hsforms.net

Forms and support

*.crisp.chat

In-app support chat


▎ Note: This list can change as Lumen5 evolves. If something stops working after a network change, re-check this page for updates or run the diagnostic above.


Other network requirements

  • Modern TLS (TLS 1.2 or higher) must be allowed.
  • WebSocket connections must be allowed (used for real-time editing and progress updates).
  • File uploads must be permitted — see below, this is the most common point of failure.


Uploads: the most common issue


Lumen5 uploads your files via storage.lumen5.com. Many upload problems come down to this

host being blocked, in one of two ways:


  1. The storage host is blocked by name or category.

Some proxies classify storage.lumen5.com as "cloud storage / file sharing" and block the whole category, even though lumen5.com itself loads fine.


  1. A content filter or DLP rule inspects and blocks the upload.

Some Data Loss Prevention (DLP) appliances inspect what's being uploaded and block recognized file types (PDFs, images, videos) while letting other traffic

through. The tell-tale sign is that some uploads work and others don't, or uploads "hang" and time out. If you see this, your IT team will need to exempt

outbound uploads to storage.lumen5.com from content/file-type inspection.


In both cases, the diagnostic at lumen5.com/diagnostic-check will tell you (and your IT team) exactly which case you're hitting.


Still stuck?


Run the diagnostic, then send the report to Lumen5 (success manager or via the in-app chat) and we'll help interpret it.

Updated on: 02/07/2026