> For the complete documentation index, see [llms.txt](https://metalbear.com/mirrord/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://metalbear.com/mirrord/docs/using-mirrord/connecting-tools/web-browsing.md). # Web Browsing Browse internal web tools in your cluster from your own browser through mirrord. You can use mirrord to browse the web as if you were inside your cluster. This is useful for accessing internal tools (like Grafana, Kibana, or ArgoCD) that are not exposed to the public internet, or for verifying that a service is reachable from within the namespace. ## Prerequisites This guide assumes you have already set up a local proxy using `microsocks` and `mirrord`. If you haven't done this yet, please follow the [setup guide](https://metalbear.com/mirrord/docs/using-mirrord/connecting-tools.md) first to launch the proxy. Once the proxy is configured, [install "SOCKS5 Configurator" Chrome extension](https://chromewebstore.google.com/detail/socks5-configurator/hnpgnjkeaobghpjjhaiemlahikgmnghb) ## Configuration 1. Ensure the prerequisite [SOCKS5 proxy](https://metalbear.com/mirrord/docs/using-mirrord/connecting-tools.md) is running with `mirrord` and targeting the desired cluster. 2. In a Chrome window: 1. Open the SOCKS5 Configurator extension 2. Make sure the "SOCKS5 Proxy" is enabled 3. Type in its respective textbox `127.0.0.1:1080` 4. Hit the save button 3. That's it! You can verify your IP address has changed via a quick "what is my ip address" search in Google ## What's next? 1. If you'd like to intercept traffic rather than mirror it so that your local process is the one answering the remote requests, check out [this guide](https://metalbear.com/mirrord/docs/using-mirrord/incoming-traffic/filter-incoming-traffic.md). Note that you can even filter which traffic you intercept! 2. If your local process reads from a queue, you might want to test out the [copy target feature](https://metalbear.com/mirrord/docs/using-mirrord/copy-target.md), which temporarily creates a copy of the mirrord session target. With its `scaledown` flag it allows you to temporarily delete all replicas in your targeted rollout or deployment, so that none competes with your local process for queue messages. 3. If you just want to learn more about mirrord, why not check out our [architecture](https://metalbear.com/mirrord/docs/reference/architecture.md) or [configuration](https://metalbear.com/mirrord/docs/config) sections? --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://metalbear.com/mirrord/docs/using-mirrord/connecting-tools/web-browsing.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.