Skip to content

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

Closed
FatGrizzly opened this issue Feb 22, 2021 · 6 comments
Closed

Additional steps to setup a custom domain previously from gitbook #7939

FatGrizzly opened this issue Feb 22, 2021 · 6 comments
Labels
Needed: documentation Documentation is required

Comments

@FatGrizzly
Copy link
Contributor

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.

@humitos
Copy link
Member

humitos commented Feb 22, 2021

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?

@davidfischer
Copy link
Contributor

@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. curl -IL https://support.infinitzhost.com/), it never reaches Read the Docs' servers. The previous person who had this problem fixed it by reaching out to both Cloudflare and GitBook support. I'm sorry I am not more helpful but hopefully that gives you enough to fix it.

@FatGrizzly
Copy link
Contributor Author

Hmm, thanks for the reply, I will contact gitbook soon and let's see what happens

@FatGrizzly
Copy link
Contributor Author

Fixed this by contacting gitbook support, and why not add a small warning for previous gitbook users in rtd?

@stsewd stsewd added the Needed: documentation Documentation is required label Feb 23, 2021
@stsewd
Copy link
Member

stsewd commented Feb 23, 2021

yeah, we could have an entry in the docs. A PR with the process you followed is welcome!

@stsewd stsewd changed the title ReadtheDocs Custom domain bug Additional steps to setup a custom domain previously from gitbook Feb 23, 2021
@FatGrizzly
Copy link
Contributor Author

#7945

@stsewd stsewd closed this as completed in f9bbb61 Feb 24, 2021
agjohnson pushed a commit that referenced this issue Mar 2, 2021
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
None yet
Development

No branches or pull requests

4 participants