diff --git a/docs/troubleshooting/connection-issues.mdx b/docs/troubleshooting/connection-issues.mdx index c9b7cb1ff..df811496d 100644 --- a/docs/troubleshooting/connection-issues.mdx +++ b/docs/troubleshooting/connection-issues.mdx @@ -6,7 +6,7 @@ description: "How to fix connection issues when the BrowserOS agent is not respo If you see **"Failed to Fetch"** or **"Unable to connect to BrowserOS agent"**, your agent has been killed. - Failed to fetch error + Failed to fetch error ## Windows: Did you allow the BrowserOS Agent? @@ -14,7 +14,7 @@ If you see **"Failed to Fetch"** or **"Unable to connect to BrowserOS agent"**, When BrowserOS starts for the first time on Windows, a popup will ask if you want to allow **BrowserOS Agent** to access the network. Click **Allow** — the agent runs as a separate process alongside the browser and needs this permission to work. If you clicked **Cancel** or missed this prompt, the agent won't be able to connect. - Allow BrowserOS Agent network access prompt + Allow BrowserOS Agent network access prompt To fix this, go to **Windows Security → Allow an app through your network settings**, and make sure **BrowserOS Agent** is enabled. @@ -26,7 +26,7 @@ To fix this, go to **Windows Security → Allow an app through your network sett Open **Settings** from the sidebar, scroll to the MCP Server section, and click **Restart**. Wait a couple of minutes. - Click Restart in MCP Server Settings + Click Restart in MCP Server Settings @@ -39,7 +39,7 @@ To fix this, go to **Windows Security → Allow an app through your network sett 4. Reopen **BrowserOS** — the agent will restart automatically. - Search for BrowserOS Agent in Task Manager and restart it + Search for BrowserOS Agent in Task Manager and restart it If the agent still doesn't reconnect, end both **BrowserOS** and **BrowserOS Agent** in Task Manager, then reopen the app. @@ -100,7 +100,7 @@ If you're still experiencing issues, reach out: Get help from the community - + Join our Slack diff --git a/docs/troubleshooting/failed-to-fetch-error.png b/docs/troubleshooting/failed-to-fetch-error.png new file mode 100644 index 000000000..204a27ff5 Binary files /dev/null and b/docs/troubleshooting/failed-to-fetch-error.png differ diff --git a/docs/troubleshooting/mcp-server-restart.png b/docs/troubleshooting/mcp-server-restart.png new file mode 100644 index 000000000..ebba81c75 Binary files /dev/null and b/docs/troubleshooting/mcp-server-restart.png differ diff --git a/docs/troubleshooting/troubleshoot-search-restart-agent-task-manager.png b/docs/troubleshooting/troubleshoot-search-restart-agent-task-manager.png new file mode 100644 index 000000000..1bd411e5f Binary files /dev/null and b/docs/troubleshooting/troubleshoot-search-restart-agent-task-manager.png differ diff --git a/docs/troubleshooting/windows-installation-allow-browseros-agent.png b/docs/troubleshooting/windows-installation-allow-browseros-agent.png new file mode 100644 index 000000000..247bf4525 Binary files /dev/null and b/docs/troubleshooting/windows-installation-allow-browseros-agent.png differ