-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Additional steps to setup a custom domain previously from gitbook #7939
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
Comments
It seems the domain was managed by gitbook at some point. I know we recently had a similar problem with another domain and @davidfischer figured it out. I didn't track it completely and I'm not sure what was the exact problem/solution, but there is some history in #7801 @davidfischer do you know what the user/us have to do here to make the custom domain to work? |
@FatGrizzly, you're right that this is extremely bizarre and we tracked it down to a Cloudflare/GitBook.com bug (relevant forum post). Basically, for some "partners" like GitBook.com, Cloudflare seems to be doing some magic with DNS resolution and directing HTTP traffic. Even though when we query DNS, your setup looks correct and we are even able to issue the certificate, you still can't reach it. While your DNS has propagated, when you do an HTTP request (eg. |
Hmm, thanks for the reply, I will contact gitbook soon and let's see what happens |
Fixed this by contacting gitbook support, and why not add a small warning for previous gitbook users in rtd? |
yeah, we could have an entry in the docs. A PR with the process you followed is welcome! |
Close #7939 Co-authored-by: Santos Gallegos <[email protected]>
Details
Expected Result
The mkdocs should be served in my custom domain.
Actual Result
It just redirects to my old gitbook knowledgebase, ah yeah, dont accuse me for dns propagation, its been 24 hours and I can confirm that it has propagated
https://www.whatsmydns.net/#CNAME/support.infinitzhost.com
Even the SSL state is active, probably a bug.
The text was updated successfully, but these errors were encountered: