Skip to main content
Add the record shown by Biqli in Cloudflare’s DNS area. During initial verification, set applicable records to DNS only so Biqli can see the expected target directly. Wait for the Biqli status to become active before changing proxy behavior. If enabling the Cloudflare proxy later causes redirects or certificate errors, return the record to DNS only and verify that no Cloudflare redirect, Worker, or conflicting record intercepts the hostname. Always use the record value displayed in Biqli. Do not copy a value from another domain.

​
Configure the record

  1. Select the correct zone in Cloudflare.
  2. Open DNS Records and create the type requested by Biqli.
  3. Enter the host and target exactly as shown.
  4. Set proxy status to DNS only for initial verification.
  5. Save and wait for public DNS to update.
  6. Return to Biqli and follow the status through HTTPS provisioning.

​
Check Cloudflare features

Redirect Rules, Page Rules, Workers, Bulk Redirects, and an existing proxy can intercept the hostname before Biqli receives the request. Temporarily disable conflicting behavior while testing. After activation, test both the root hostname and a real short URL over HTTPS. If enabling the orange-cloud proxy introduces a redirect loop, certificate warning, or wrong origin, return to DNS only and review the Cloudflare SSL mode and routing rules. Cloudflare account access is never required by Biqli support. Share DNS values, not credentials.