English

বাংলা
हिन्दी

English

বাংলা
हिन्दी

Appearance

Cloudflare settings for APNCloud hosting ​

A wrong Cloudflare setting can make a working website stop opening. Use the settings in this guide for websites on APNCloud hosting. Cloudflare menus sometimes move, so follow the names, not the position on the screen.

Do not use the "Flexible" SSL/TLS mode

In Flexible mode Cloudflare connects to our servers over plain HTTP. Our servers send every HTTP request to HTTPS, so the request goes round and round, and visitors see "too many redirects". Use Full. Use Full (strict) only when the certificate is ready, as described below.

Before you begin ​

Steps ​

  1. In Cloudflare open DNS, then Records. For a new domain, set Proxy status of the website records (@ and www) to DNS only (grey cloud).

  2. In the hosting panel, request the free SSL certificate for the domain and for www. Wait until the panel shows that the certificate is issued for both names.

  3. In Cloudflare open SSL/TLS, then Overview, and choose Full.

  4. Go back to DNS, then Records, and turn the website records (@ and www) to Proxied (orange cloud).

  5. Open the website and check that it loads over HTTPS without errors.

  6. Now choose Full (strict) in SSL/TLS, then Overview. Do this only when the hosting panel shows an issued certificate for the domain and for www. If you choose it too early, visitors see error 526.

  7. Open SSL/TLS, then Edge Certificates. Turn on Always Use HTTPS. Set Minimum TLS Version to TLS 1.2. You can also turn on Automatic HTTPS Rewrites, which helps with mixed content.

  8. Keep mail, FTP and other non-web records on DNS only (grey cloud). The Cloudflare proxy does not carry mail or FTP traffic:

    RecordProxy status
    @ and www (website)Proxied, after the SSL certificate is issued
    mail, ftp and other non-web namesDNS only
    MX recordsDNS only (no proxy option)

  9. Make sure no firewall rule blocks /.well-known/acme-challenge/. The free SSL certificate needs this path to be issued and renewed. If you use Security rules, add a rule that allows this path before your other rules:

    text
    (starts_with(http.request.uri.path, "/.well-known/acme-challenge/"))

  10. Check from your computer. When the proxy is on, curl -I https://example.com shows server: cloudflare and no redirect loop.

Your site already has a valid certificate?

If the hosting panel already shows a valid certificate for the domain and for www, you can skip step 2 and go straight to Full (strict).

Common mistakes ​

  • Choosing Flexible. This causes the redirect loop described above.
  • Choosing Full (strict) before the certificate is issued for both the domain and www.
  • Turning the orange cloud on for mail or ftp records. Mail and FTP stop working.
  • Blocking /.well-known/acme-challenge/ with a firewall rule, a country block or Bot Fight Mode. The certificate then cannot be issued or renewed.
  • Redirecting to HTTPS in several places at the same time, for example Cloudflare, a plugin and the .htaccess file.

Need help? ​

Open a support ticket in the Client Area or contact [SUPPORT_CONTACT]. Tell us the domain, the SSL/TLS mode you chose and any error code you see.

Last reviewed ​

2026-10-29