> For the complete documentation index, see [llms.txt](https://doc.wearepatchworks.com/product-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.wearepatchworks.com/product-documentation/getting-started/patchworks-quickstart-guide/troubleshooting-dashboard-and-login-issues.md).

# Troubleshooting dashboard & login issues

If you're experiencing general issues with the Patchworks dashboard - such as being logged out unexpectedly, images or icons not loading, or pages failing to load fully - the cause is often **not Patchworks itself**, but security software running on your company network or device.

### Common symptoms

| Symptom                                                                       | Likely cause                                                                     |
| ----------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| Logged out unexpectedly or repeatedly                                         | Session cookies being stripped or modified by a corporate proxy / TLS inspection |
| Images, icons, or fonts not loading                                           | Asset/CDN domains blocked or filtered by network security tools                  |
| Pages partially loading or appearing broken                                   | Scripts or API calls blocked by a firewall, proxy, or browser policy             |
| Live updates not appearing (e.g. run logs)                                    | WebSocket connections blocked by a proxy or VPN                                  |
| Browser prompt: *"Look for and connect to any device on your local network?"* | Chrome's Local Network Access permission (see below)                             |

### Corporate security tools

Tools such as **Zscaler (ZIA/ZPA)**, **Netskope**, **Cisco Umbrella**, **Palo Alto Prisma Access**, and similar zero-trust/proxy products inspect and sometimes modify web traffic. This can interfere with authentication cookies, blocked asset domains, and real-time connections.

{% hint style="info" %}
**Example: Chrome 142 & Zscaler.** From Chrome 142, Google introduced a Local Network Access permission. When a site attempts to reach addresses Chrome classes as local - including the synthetic IP ranges used by Zscaler Private Access - Chrome shows a permission prompt. If **Block** is selected, the connection fails and the application won't load. See [Zscaler's advisory](https://trust.zscaler.com/private.zscaler.com/posts/26216) for details and the recommended enterprise policy fix.
{% endhint %}

### What to try

1. **Test on a different network** - if the dashboard works on a personal device or home/mobile network, the issue is almost certainly your corporate network or security software.
2. **Check for browser permission prompts** - if you've previously clicked *Block* on a Chrome local network prompt, re-allow it via the padlock/site settings icon in the address bar.
3. **Ask your IT team to allowlist Patchworks** - traffic to Patchworks domains should be excluded from TLS inspection and content filtering.
4. **Ensure WebSocket traffic is permitted** to Patchworks domains.
5. **Still stuck?** Contact Patchworks support with your browser version, network setup (VPN/proxy in use), and a screenshot of any errors in the browser console.