Skip to main content

Troubleshooting Browser Login Issues and Blank Screens

If you’re unable to access Coalesce after logging in, or you see a blank or spinning screen, the issue is often related to network restrictions or blocked domains. These problems commonly occur in secured corporate environments where firewalls, VPNs, or SSL inspection tools interfere with required Coalesce services.

This guide explains how to identify and resolve browser-based login issues and blank screens.

Network and Firewall Configuration​

The most common cause of blank or frozen screens is network filtering that blocks required Coalesce domains. Work with your IT or network team to allowlist the following domains for outbound HTTPS traffic:

  • https://storage.coalescesoftware.io/
  • https://app.coalescesoftware.io
  • https://*.app.coalescesoftware.io
  • https://firestore.googleapis.com
  • https://firebasestorage.googleapis.com/
  • https://identitytoolkit.googleapis.com/
  • https://securetoken.googleapis.com/
Allowlist Base Domains, Not Version-Specific Paths

Allowlist the base domains (for example, storage.coalescesoftware.io), not version-specific URLs. Versioned paths change with each release and will break when Coalesce updates.

When these domains are blocked, essential assets such as configuration panels, authentication components, and Workspace data cannot load.

If you use EU, APAC, or AWS regions, see Network Requirements for the full list of regional domain variants.

Review all Network Requirements

Browser Troubleshooting Steps​

Before making network changes, try these browser troubleshooting steps:

  1. Test in a private or incognito window to rule out browser extensions or cached data.
  2. Clear cache and cookies for both Coalesce and any identity providers used for login.
  3. Try a different browser. Coalesce officially supports Google Chrome.
  4. Verify your login URL format. Use your organization’s subdomain instead of the generic login page:
    https://yourorg.app.coalescesoftware.io

Network security tools such as corporate VPNs, SSL inspection, and services like ZScaler can interfere with Coalesce authentication and UI loading.
If you encounter persistent loading screens or CORS (Cross-Origin Resource Sharing) errors, confirm that your organization’s security tools aren’t filtering or modifying Coalesce traffic. CORS errors often indicate that a proxy or firewall is blocking or modifying responses, rather than a Coalesce configuration issue.

SSO-Specific Issues​

If your organization uses Single sign-on (SSO), confirm that both configuration and network access are correct.

Check that:

  • All SSO fields are configured correctly, including Authority, Subdomain, Authorization Server, and OIDC Client ID.
  • Network policies allow outbound access to Coalesce IP addresses for your region.
  • Redirect URIs in your identity provider configuration match exactly with those in Coalesce.

When to Contact Your IT Team​

If the issue continues after following these steps:

  • Review corporate firewall and proxy logs for blocked Coalesce domains.
  • Confirm that all domains listed in the Network and Firewall Configuration section are allowlisted.
  • Check for SSL inspection or content filtering on the listed domains.
  • If your firewall flags storage.coalescesoftware.io as malware, this is typically a false positive. A VirusTotal scan of the CDN content can verify that it's safe.