> 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-should-i-access-replica.md). # How should I access Replica? Replica is delivered as a web application accessible via the public internet, at a customer-specific URL. Replica uses HTTPS and WebSocket to deliver a secure and high-performance experience. For best results, ensure your connection meets the following requirements: * Connect directly to your Replica instance. Connecting through a VPN, remote browser, proxy, or virtualized desktop environment can cause decreased performance or compatibility issues. Common examples could include Zscaler, Akamai, or Citrix. * Use a modern, up-to-date web browser. Replica is continually updated to support the current version of all major web browsers. * If your organization utilizes security software that intercepts or blocks network traffic, be sure it is configured to whitelist connections to your Replica instance address to ensure proper operation. * Ensure you have a good quality internet connection. If you are connected via WiFi, ensure you have a strong signal free from interference. You should use an ethernet connection if one is available to you. --- # 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-should-i-access-replica.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.