mirror of
https://github.com/mintlify/docs.git
synced 2026-09-14 13:35:46 +08:00
mintlify[bot]
f8e015ff62
* Improve SEO metadata: update descriptions to 130-155 chars across 177 pages Generated-By: mintlify-agent * Apply suggestion from @ethanpalm * Apply suggestions from code review Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com> * 💅 --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> Co-authored-by: Ethan Palm <56270045+ethanpalm@users.noreply.github.com>
34 lines
1.7 KiB
Plaintext
34 lines
1.7 KiB
Plaintext
---
|
|
title: "External proxies with Vercel"
|
|
description: "Configure external reverse proxies like Cloudflare or Nginx in front of your Vercel deployment to serve Mintlify docs at a custom subpath."
|
|
keywords: ["Vercel", "external proxy", "CloudFront", "domain verification", "SSL certificates"]
|
|
---
|
|
|
|
If you have an external proxy like Cloudflare or AWS CloudFront in front of your Vercel deployment, you must configure it properly to avoid conflicts with Vercel's domain verification and SSL certificate provisioning.
|
|
|
|
Improper proxy configuration can prevent Vercel from provisioning Let's Encrypt SSL certificates and cause domain verification failures.
|
|
|
|
See the [supported providers](https://vercel.com/guides/how-to-setup-verified-proxy#supported-providers-verified-proxy-lite) in the Vercel documentation.
|
|
|
|
## Required path allowlist
|
|
|
|
Your external proxy must allow traffic to these specific paths without blocking, redirecting, or heavily caching:
|
|
|
|
- `/.well-known/acme-challenge/*` - Required for Let's Encrypt certificate verification
|
|
- `/.well-known/vercel/*` - Required for Vercel domain verification
|
|
- `/mintlify-assets/_next/static/*` - Required for static assets
|
|
|
|
These paths should pass through directly to your Vercel deployment without modification.
|
|
|
|
## Header forwarding requirements
|
|
|
|
Ensure that your proxy correctly forwards the `HOST` header. Without proper header forwarding, verification requests fail.
|
|
|
|
## Testing your proxy setup
|
|
|
|
To verify your proxy is correctly configured:
|
|
|
|
1. Test that `https://[yourdomain].com/.well-known/vercel/` returns a response.
|
|
2. Ensure SSL certificates are provisioning correctly in your Vercel dashboard.
|
|
3. Check that domain verification completes successfully.
|