Who this is for: IT and network administrators at organizations whose corporate firewall, proxy, or VPN restricts outbound traffic. If Vidmob (acs.vidmob.com) fails to load, shows a blank screen, can't log in via SSO, or assets won't upload or play, your network is likely blocking one or more of the domains below.
Quick start: Allowlisting *.vidmob.com plus the AWS storage and Amazon Cognito domains in the Required section covers core access for most customers. Add the other sections based on the features your team uses.
Required - core application
Domain | Purpose |
| Main application, APIs, real-time services, CDN, and invitation links (includes |
| Real-time connections (chat, live updates, AI assistants) |
| Single Sign-On (SSO) and authentication — required for SSO logins |
| Creative asset storage, upload, and download |
| Asset delivery network |
Required - fonts and supporting services
Domain | Purpose |
| Google Fonts (web fonts) |
| Google Sign-In (required if your team logs in with Google) |
| Google Drive asset import (required if your team imports creatives from Google Drive) |
| Web fonts |
Recommended - support and in-app help
Blocking these won't break the core application, but you'll lose in-app support chat, product guidance, and the diagnostics Vidmob uses to troubleshoot issues you report.
Domain | Purpose |
| In-app support chat and help center |
| Invitation and onboarding links |
| Performance and error diagnostics |
| Product usage analytics |
| Analytics tag manager (diagnostics; degrades silently if blocked) |
Feature-specific - allowlist only if you use the feature
Domain | Feature |
| Video playback |
| Stock media and icon libraries |
| Payments |
Recommended Network Configuration for Vidmob's Maddie (AI-powered assistant)
To ensure Vidmob's Maddie SDK initializes and functions correctly across your network, we recommend allowing the wildcard domain *.eucerahive.io rather than whitelisting each subdomain individually.
Why We Recommend the Wildcard:
Simplified Management: A single wildcard entry covers all four active services (SDK delivery, analytics, session recording, and AI backend) in one rule.
Future-Proofing: If we introduce new subdomains to support future features or performance optimizations, your network configuration will not require manual updates or cause service interruptions.
Note: The wildcard *.eucerahive.io only matches subdomains and does not apply to the apex domain eucerahive.io (which is not required for the SDK).
Content Security Policy (CSP) Configuration
If your application enforces a browser-level Content Security Policy (CSP), please ensure the wildcard is also applied there. You can use the following optimized policy:
Content-Security-Policy:
script-src 'self' 'unsafe-inline' https://*.eucerahive.io;
connect-src 'self' https://*.eucerahive.io;
style-src 'self' 'unsafe-inline';
Per-Directive Reference:
script-src: Allows loading the core SDK loader, session recorder, and agent panel scripts.connect-src: Enables real-time communication with the AI agent backend, feature flag updates, and session recording uploads.style-src: Required to allow the agent panel to inject its visual styling and layout attributes at runtime.
Still having trouble?
If Vidmob still won't load after allowing the Required domains, contact support@vidmob.com with the URL that fails, a screenshot of your browser console (press F12, then open the Console tab), and any blocked-request errors shown there. These usually pinpoint the exact domain your network is filtering.