christophelec commented 5 years ago

Checklist

[X] I have checked the issues list for similar or identical bug reports.
[X] I have checked the pull requests list for existing proposed fixes.
[X] I have checked the commit log to find out if the bug was already fixed in the master branch.
[X] I have included all related issues and possible duplicate issues in this issue (If there are none, check this box anyway).

Related Issues and Possible Duplicates

Related Issues

None

Possible Duplicates

None

Description

Using the search engine on the documentation, I followed the first link : https://docs.celeryproject.org/en/latest/userguide/configuration.html?highlight=backend which results in an SSL_ERROR_BAD_CERT_DOMAIN.

It seems the SSL certificate is only valid for readthedocs.org, not celeryproject

To reproduce : search for anything, for example http://docs.celeryproject.org/en/latest/search.html?q=backend&check_keywords=yes&area=default and follow a link

Suggestions

I'm not sure I'm well placed to offer recommandation, but either providing a correct certificate via let's encrypt, or disabling https altogether could fix the issue

spheron1 commented 5 years ago

Judging by https://docs.readthedocs.io/en/stable/custom_domains.html#custom-domain-ssl, it looks like a change is required for the docs.celeryproject.org CNAME DNS record from "celery.readthedocs.org" to "readthedocs.io" so that the site is proxied via CloudFlare and they can issue an SSL certificate for the custom domain.

hartwork commented 5 years ago

I would like to raise urgency here. The net is full of https links to celery docs (and rightfully so in my opinion) so it would be nice to get this fixed sooner than latter. Thanks!

jerr0328 commented 5 years ago

Looks like a duplicate of #24, should continue to push there.

celery / celeryproject