Skip to content

Docs: missing information on Cloudflare to Cloudflare proxy configuration #11371

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
agjohnson opened this issue May 30, 2024 · 4 comments · Fixed by #11734
Closed

Docs: missing information on Cloudflare to Cloudflare proxy configuration #11371

agjohnson opened this issue May 30, 2024 · 4 comments · Fixed by #11734
Labels
Needed: documentation Documentation is required

Comments

@agjohnson
Copy link
Contributor

I was looking for these directions to point a user to them but could not find them in the docs anymore.

From the translation file:

"Due to a limitation, a domain cannot be proxied on Cloudflare to another "
"Cloudflare account that also proxies. This results in a \"CNAME Cross-User "
"Banned\" error. In order to do SSL termination, we must proxy this "
"connection. If you don't want us to do SSL termination for your domain -- "
"**which means you are responsible for the SSL certificate** -- then set your"
" CNAME to ``cloudflare-to-cloudflare.readthedocs.io`` instead of "
"``readthedocs.io``."

Perhaps we removed this on purpose, as it's not a common configuration?

@stsewd
Copy link
Member

stsewd commented May 30, 2024

I think it was removed because it was no longer a problem 🤷‍♂️

@agjohnson
Copy link
Contributor Author

In that users can just use the standard CNAME with their own Cloudflare account? I guess we'll see. I had a user note that they had problems using their own Cloudflare account in front of us and mentioned the record as a fix.

@stsewd
Copy link
Member

stsewd commented Oct 29, 2024

So, yeah, looks like users need to uncheck the "proxy" option when creating a CNAME. And we shouldn't recommend using the cloudflare-to-cloudflare.readthedocs.io target, as that points directly to our LB, and we are required to use CF for addons now.

@stsewd stsewd added the Needed: documentation Documentation is required label Oct 29, 2024
@github-project-automation github-project-automation bot moved this to Planned in 📍Roadmap Oct 30, 2024
@humitos
Copy link
Member

humitos commented Oct 30, 2024

I'm putting this issue in Q4 so we update this docs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: documentation Documentation is required
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants