Update from support feedback: custom domain topology and subpath verification - #7255
Closed
mintlify[bot] wants to merge 7 commits into
Closed
mintlify[bot] wants to merge 7 commits into
mintlify[bot] wants to merge 7 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
ethanpalm
self-requested a review
September 14, 2026 16:56
ethanpalm
reviewed
Sep 14, 2026
ethanpalm
reviewed
Sep 14, 2026
ethanpalm
reviewed
Sep 14, 2026
ethanpalm
reviewed
Sep 14, 2026
Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
…xies Cloudflare's own TXT-based domain control validation resolves via a plain DNS lookup and doesn't depend on traffic routing, except for domains already proxied through Cloudflare, where it requires traffic to reach Mintlify's edge first (matching the existing Cloudflare-proxied domains section). The added content generalized that Cloudflare-specific behavior to all subpath reverse proxies, which would misdirect Vercel/ AWS/nginx customers whose records should verify normally. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Brings the es/fr/zh copies of custom-domain.mdx, docs-subpath.mdx, and the cf-custom-hostname help article in line with the English correction: the TXT-record verification behavior is specific to subpath proxies running on Cloudflare, not all reverse proxies. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
# Conflicts: # docs.json # es.json # fr.json # zh.json
- Use "project" for the site entity to match the terminology change on main; keep the literal server error string unchanged. - Point dashboard links at /settings/project/custom-domain. - Use <your-subdomain>.mintlify.site as the proxy target; mintlifysite.com is the auth-only origin and subpaths don't support auth. - Name the re-verify button by its actual tooltip, "Re-verify domain". - Mirror all changes into es, fr, and zh. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two support threads needed human help because the docs don't state that a custom domain connects to exactly one deployment, or that the verification
TXTrecords shown in the dashboard stay unverified (harmlessly) when a customer's own reverse proxy serves the docs subpath. This adds two help center articles covering those questions, short cross-linking notes on the custom domain and subpath pages, and mirrored translations.Changes
customize/custom-domainanddeploy/docs-subpathlinking to both articles; corrected the claim that the dashboard hides DNS records for subpath setups.es.json/fr.json/zh.jsonnavigation entries).Support context
Note
Low Risk
Documentation and navigation-only changes; no application code, auth, or data handling.
Overview
Adds help-center coverage for two common custom-domain support gaps: one domain maps to one Mintlify project (multi-product patterns via path navigation or subdomains), and Cloudflare subpath proxies where dashboard
_cf-custom-hostname/_acme-challengeTXT records stay unverified harmlessly.Custom domain and Host docs at a subpath now tell subpath-proxy customers to follow reverse-proxy guides instead of adding the dashboard
CNAME, link the new articles, and add a subpath note about skippingCNAMEand expected unverified TXT on Cloudflare. The retry step label is updated to Re-verify domain to match the dashboard.The two articles and page edits are mirrored in French, Spanish, and Chinese, with Help center nav entries in
docs.jsonand locale JSON files.Reviewed by Cursor Bugbot for commit 7aeddce. Bugbot is set up for automated code reviews on this repo. Configure here.