Network & firewall requirements

If iMeshh Pro won't load on a work or corporate network, it's almost always a firewall, proxy, or VPN blocking one of the services the app needs to reach. This page lists exactly what to allow so your IT or network team can unblock it. It's written to be forwarded as-is to whoever manages your network.

The error this fixes

If you see a message like this, you're in the right place:

We can't reach the server. Your account is fine — we couldn't load your workspace. This is usually a network, VPN, or firewall issue rather than a problem with your account.

It means your browser reached the iMeshh website but couldn't reach the backend service that loads your workspace. On a locked-down network, that service is the thing most likely to be blocked.

Quick test for your IT team (30 seconds)

Before changing anything, confirm it really is the network:

1. On the affected computer, open this link in a browser: https://api.imeshh.app/v1/health
   • If it shows a short "ok" response, the connection is getting through — contact us and we'll look closer.
   • If it fails, times out, or is blocked, the network is blocking our backend. The list below is what to allow.
2. As a cross-check, open iMeshh on a phone on mobile data (off the office Wi-Fi and VPN). If it works there but not at the desk, it's the office network.

What to allow

Everything below is standard outbound HTTPS on port 443. These are the same services every iMeshh Pro browser session uses.

Required — the app won't load without these

Domain	What it's for
pro.imeshh.com	The iMeshh Pro web app
api.imeshh.app	The backend service that loads your workspace (most commonly the blocked one)
imeshh-api.office-e09.workers.dev	Backup host for the backend
yolsxftwvzzybeokzggo.supabase.co	Sign-in and live updates — needs HTTPS and WebSocket (WSS) on 443
e0994c7e566fc631ae6de5bcc6ad20a4.r2.cloudflarestorage.com	Asset, image, and file storage (and its subdomains)
imeshhjson.imeshh.com, r2.imeshh.com	Thumbnails and image delivery

Optional — only needed for specific features

Domain	What it's for
js.stripe.com, api.stripe.com	Billing and payment pages
challenges.cloudflare.com	Security check shown on some sign-in and checkout steps
player.vimeo.com, *.vimeocdn.com	Tutorial and intro videos
us.i.posthog.com, us-assets.i.posthog.com	Anonymous product analytics (safe to skip)

Ports and protocols

• Outbound TCP 443 (HTTPS) to every domain above.
• WebSocket (WSS) on port 443 to *.supabase.co — the workspace uses it for live updates. If WebSocket upgrades are blocked while plain HTTPS is allowed, your workspace still won't load.
• No other inbound or outbound ports are needed.

Notes for your IT team

• Allow WebSocket (WSS) upgrades to *.supabase.co, not only standard HTTPS.
• Allow the .app top-level domain. Some content filters block newer domain endings by category — api.imeshh.app is our backend and has to be reachable.
• If you use SSL/TLS inspection (deep packet inspection / a decrypting proxy), exclude these domains or make sure the inspection doesn't break their certificates or WebSocket connections.
• VPN users: if your VPN routes all traffic through a filtered gateway, the same rules have to apply there — or test with the VPN off to confirm.

Still not working

If the app still won't load after allowing the domains above, contact support through the help bubble in the bottom-right corner of the app, or email support@imeshh.com. To help us pinpoint it fast, include:

• The result of the https://api.imeshh.app/v1/health test above.
• Your network setup: VPN, proxy, or company firewall, and whether it worked on mobile data.
• Roughly where you're based, so we can rule out a regional routing issue.