> For the complete documentation index, see [llms.txt](https://docs.simptel.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.simptel.com/tf-platform/administration/organizations/projects/tenants/domains/reverse-proxies/cloudflare-as-reverse-proxy.md).

# Cloudflare as Reverse Proxy

This article provides a steps to configure Cloudflare as a reverse proxy for your application.

#### Steps to Configure Cloudflare

1. **Sign Up for Cloudflare**
   * **Create a Cloudflare Account**: If you don’t already have an account, sign up on Cloudflare's website.
   * **Add Your Domain**: Follow the prompts to add your domain to your account.
2. **Update DNS Settings**
   * **Verify Domain Ownership**: Follow the instructions to verify ownership, typically by adding a TXT record at your domain registrar.
   * **Change DNS Records**:
     * Go to the **DNS** tab in your Cloudflare dashboard.
     * Add or modify DNS records to point to your origin server using the following settings:
       * **Type**: A or CNAME
       * **Name**: Your subdomain (e.g., platform or www)
       * **Value**: Your origin server’s IP address or hostname
       * **Proxy Status**: Set to **Proxied** (indicated by the orange cloud icon).
3. **Configure SSL/TLS Settings**
   * **Set SSL/TLS Mode**: Navigate to the **SSL/TLS** tab and choose an appropriate mode (e.g., Full or Full (strict)). If you have added the origin server certificate as a custom certificate in the platform, use **Full (strict)**.
   * **Enable Always Use HTTPS**: Turn on the **Always Use HTTPS** option to ensure secure connections.
4. **Test Your Setup**
   * **Access Your Tenant**: Ensure your tenant is accessible through the Cloudflare proxy. Verify that SSL/TLS functionality works and that requests are routing correctly to your origin server.


---

# 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.simptel.com/tf-platform/administration/organizations/projects/tenants/domains/reverse-proxies/cloudflare-as-reverse-proxy.md?ask=<question>&goal=<user_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.