Thank you for the info, that is a network error, as you can see in the Dev Tools panel:
403 Forbidden.
If it works on Edge outside your work network but not in Chrome or Firefox on your work device or network, it’s almost certainly related to:
🧱 Work Network, Proxy, or Security Software
- Corporate proxies or firewalls might:
- Strip headers (e.g.
Cookie,Authorization,X-CSRF-TOKEN) - Block specific routes (like anything with
/api,/auth, etc.) - Intercept SSL/TLS (yes, some companies install their own root CA to decrypt HTTPS traffic)
- Antivirus or endpoint protection (like McAfee, CrowdStrike, Symantec):
- May interfere with browser traffic or block some scripts/cookies.
- VPN:
- These sometimes route traffic through their own tunnel and can be overly aggressive with blocking.
- Group policy/browser settings:
- On managed devices, things like tracking protection, third-party cookie blocking, or even JavaScript restrictions could be enforced.
There is nothing we can do on our side, aside from catching those network errors and display a troubleshooting page. We will try to add that in a future update.
Sorry for the inconvenience.