Documentation temporarily offline
-
While updating our documentation website https://docs.ubports.com we've run into trouble with the configuration. Unfortunately that means that the docs site is not reachable at the moment. We're working on a solution.
Apologies and hopefully we can fix this soon.
For now the best stop gap is probably the last wayback version https://web.archive.org/web/20250114230013/https://docs.ubports.com/en/latest/
-
Let me add some background (maybe someone has previous experience with this)
The source code for the docs used to be at https://github.com/ubports/docs.ubports.com/ and hosted by Read The Docs at http://docsubportscom.readthedocs.io with the custom domain docs.ubports.com configured in this RTD project. The cloudflare DNS points docs.ubports.com to readthedocs.io and that setup worked alright in the past.
In order to move over to the new repo at https://gitlab.com/ubports/docs/docs.ubports.com we've created a new RTD project at http://docsubportscom-gitlab.readthedocs.io and moved the custom domain over to this new project. But now we're faced with a "CNAME Cross-User Banned" Error 1014 instead of our docs
Contacted RTD support to see if they can help.
-
hmmm according to the error this is the issue:
The host is configured as a CNAME across accounts on Cloudflare, which is not allowed by Cloudflare's security policy.
are the two separate accounts?it also says:
If this is an R2 custom domain, it may still be initializing. If you have attempted to manually point a CNAME DNS record to your R2 bucket, you must do it using a custom domain.
Could it be just dns intialization? do we have other logs in the dashboard?also http://docsubportscom.readthedocs.io/ still works, so perhaps that could be a stopgap until we figure this out
-
@Fuseteam said in Documentation temporarily offline:
hmmm according to the error this is the issue:
The host is configured as a CNAME across accounts on Cloudflare, which is not allowed by Cloudflare's security policy.
are the two separate accounts?yes. both Cloudflare, but that was also true with the old setup. not clear what's different now
it also says:
If this is an R2 custom domain, it may still be initializing. If you have attempted to manually point a CNAME DNS record to your R2 bucket, you must do it using a custom domain.
Could it be just dns intialization? do we have other logs in the dashboard?I don't have access to any other logs. not sure what R2 is or whether that applies to us. Not sure what this initialization is about, but the problem hasn't resolved itself since yesterday, so, I'm guessing ... whatever initialization might have been going on should have completed but that doesn't seem to have made a difference ...
also http://docsubportscom.readthedocs.io/ still works, so perhaps that could be a stopgap until we figure this out
yeah. if it works it works and can of course be used. At some point yesterday it didn't work either, but yeah, the links are there
-
@doniks said in Documentation temporarily offline:
yes. both Cloudflare, but that was also true with the old setup. not clear what's different now
I mean is the same user for http://docsubportscom.readthedocs.io/ and http://docsubportscom-gitlab.readthedocs.io/?
could it be that to cloudflare docs.ubports is from one user and is now "hijacked" by another?i also tried running
dig docs.ubports.com
and i got this as output:; <<>> DiG 9.18.30-0ubuntu0.24.04.1-Ubuntu <<>> docs.ubports.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31353 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;docs.ubports.com. IN A ;; ANSWER SECTION: docs.ubports.com. 300 IN CNAME readthedocs.io. readthedocs.io. 300 IN A 104.16.254.120 readthedocs.io. 300 IN A 104.16.253.120 ;; Query time: 287 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP) ;; WHEN: Fri Jan 17 10:26:19 -03 2025 ;; MSG SIZE rcvd: 105
But i am unsure if this is correct, as i don't have an output of how it was before