> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/faqs/how-do-i-troubleshoot-issues-with-a-website-in-my-virtual-environment.md). # How do I troubleshoot issues with a website in my Virtual Environment? The most common reason that you may experience issues with a third-party website, is when it is inaccessible due to technical difficulties with the website itself. If you have trouble with one website, but not others, this typically indicates an issue with that website itself. Some website operators block connections based on location or behavior of those connecting to it. If you suspect you are being blocked based upon your location, you may try connecting from another Egress location. If changing your egress doesn't work you may also want to try changing your browser image (e.g. Chromium to Firefox) because some sites will block you based on your browser and other attribution elements. If you are running scripts or scrapers against a website, be mindful to limit the rate by which they run. Many websites intentionally block or serve CAPTCHAs when they suspect a visitor is not human. --- # 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://docs.replicacyber.com/faqs/how-do-i-troubleshoot-issues-with-a-website-in-my-virtual-environment.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.