-
Notifications
You must be signed in to change notification settings - Fork 11
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
docs.celeryproject.org and celeryproject.org are down #52
Comments
Hey @colons 👋, We also offer priority support for our sponsors. |
I am experiencing the same problem using Google DNS ❯ nslookup celeryproject.org 8.8.8.8
❯ nslookup docs.celeryproject.org 8.8.8.8
❯ nslookup docs.celeryproject.org 8.8.4.4
❯ nslookup celeryproject.org 8.8.4.4 All give the same error:
|
Maybe see #21 also? |
I can't reproduce this: dig +short docs.celeryproject.org
readthedocs.io.
104.17.33.82
104.17.32.82 Hmm, maybe it's a Google DNS issue: dig @8.8.8.8 +short docs.celeryproject.org ...produces no output. |
I'm able to reproduce on non-Google DNS. Getting a |
+1 also down for me failing with nslookup and dig: nslookup celeryproject.org 9.9.9.9 # Quad9DNS
nslookup celeryproject.org 208.67.222.222 # OpenDNS
nslookup celeryproject.org 8.8.8.8 # GoogleDNS
# ** server can't find celeryproject.org: SERVFAIL
dig docs.celeryproject.org
# QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 |
If anyone needs access to the docs in a pinch... |
I changed networks, and it's no longer resolving for me:
Edit: To clarify, I moved to a network that's using a local DNS resolver + Cloudflare DNS as an authority (1.1.1.1). |
Tested manually. Ignore failing checks due to celery docs website down (https://github.com/celery/celery/issues/7351).
I am using the latest snapshot captured from web archive: https://web.archive.org/web/20220313093531/https://docs.celeryproject.org/en/stable/ |
I am seriously considering registering a new domain and start working on github page based website, later can deploy it to some VPS, I can do it. It's a long overdue |
It seems quite crazy that the owner of the domain seems to be completely unknown to maintainers... |
You should really consider getting the original domains back before they fully expire (and thus can be grabbed by someone else) - otherwise there's a good chance they'll be abused for spam or worse. |
For anyone here who needs Celery doc while this gets worked out: |
Does controlling the celeryproject.org domain give control of any email addresses that could be used to recover passwords on e.g. Github or PyPI? |
The public email on the github profile of @ask is [email protected], so at least someone could impersonate her. Whether or not her github account would be at risk is impossible to tell. PyPi doesn't disclose any emails connected to the user accounts. She is still listed as a maintainer over there, but the main contact email is that of auvipy. |
It seems that the DNS for docs.celeryproject.org may have been compromised or at least the site shouldn't be trusted at this point? The DNS is now resolving to a Russian hosting company and the certificate is for a different domain: DNS response:
Whois info:
Cert info:
|
he is not active anymore from late 2016, so we bought some new domains, and using https://docs.celeryq.dev/en/stable/. |
@auvipy I don't think that's a great long term plan, leaving broken links is bad but worse is if they potentially go somewhere hostile now. I can get in contact with Ask if that's the limiting factor. |
US is Hostile to many, so embrace it. you can try, as I am trying for last 6 years. good luck with that. |
@auvipy I am sorry to revisit this point (and also sorry if this is not the best channel), but would you be able to confirm for me that there are no '@celeryproject.org' addresses with maintainer rights for Celery on PyPI? I can still see 'ask' listed on there and the changelog implies that she was using [email protected]. My concerns are that if the Celery maintainers no longer have control of this MX for celeryproject.org then it is not possible to rule out a bad actor impersonating [email protected], using the PyPI password reset, and having write access to the package. |
The only existing user on PyPI (@ask) with a celeryproject.org address has been deactivated. No account activity has been noted since the domain was compromised. |
Just to add to @mrmonkington's concerns... Our office is now blocking celeryproject.org because its within Russia. So the possibility of it being compromised was just ratcheted up a few notches. |
The Celery team [has not had full control][1] of their celeryproject.org domain for well over a year. The domain is now [compromised][2] and redirects requests to a third party. The Celery team has [acquired a new domain][3], [docs.celeryq.dev][4]. Usage of the old domain should be urgently discontinued. [1]: celery/celeryproject#44 (comment) [2]: celery/celeryproject#52 [3]: celery/celeryproject#52 (comment) [4]: https://docs.celeryq.dev
The Celery team [has not had full control][1] of their celeryproject.org domain for well over a year. The domain is now [compromised][2] and redirects requests to a third party. The Celery team has [acquired a new domain][3], [docs.celeryq.dev][4]. Usage of the old domain should be urgently discontinued. [1]: celery/celeryproject#44 (comment) [2]: celery/celeryproject#52 [3]: celery/celeryproject#52 (comment) [4]: https://docs.celeryq.dev
The Celery team [has not had full control][1] of their celeryproject.org domain for well over a year. The domain is now [compromised][2] and redirects requests to a third party. The Celery team has [acquired a new domain][3], [docs.celeryq.dev][4]. Usage of the old domain should be urgently discontinued. [1]: celery/celeryproject#44 (comment) [2]: celery/celeryproject#52 [3]: celery/celeryproject#52 (comment) [4]: https://docs.celeryq.dev
The Celery team [has not had full control][1] of their celeryproject.org domain for well over a year. The domain is now [compromised][2] and redirects requests to a third party. The Celery team has [acquired a new domain][3], [docs.celeryq.dev][4]. Usage of the old domain should be urgently discontinued. [1]: celery/celeryproject#44 (comment) [2]: celery/celeryproject#52 [3]: celery/celeryproject#52 (comment) [4]: https://docs.celeryq.dev
The old domain has been compromised. See celery/celeryproject#52 for more information.
Looks like there may have been a compromise with the account at the hosting company, A Small Orange. Might be worth contacting them or Enom because I'm sure they wouldn't appreciate takeovers. NS Records still point to there and nothing in WHOIS has changed since April of last year:
|
The old domain has been compromised. See celery/celeryproject#52 for more information.
Good news, as of a few minutes ago the transfer of this domain has started and will be registered in perpetuity by the Python Software Foundation. Celery project maintainers can contact [email protected] to discuss next steps and management of the domain moving forward. |
@ewdurbin Great to hear. We'd love to get the Google results working again, so let me know if you want to re-point |
Just an update: still waiting for transfer to complete. Will confirm here and respond to the celery project rep at that time. |
I've moved the DNS NS records to Gandi for now, but that may take some time to propagate. |
For the time being I have configured apex, www, and docs .celeryproject.org to temporary redirect to docs.celeryq.deva |
i reached the infra team please check. |
Apologies! I responded yesterday but mishandled the To: field and didn't include you. You should have an email in your inbox now. |
Checklist
for similar or identical bug reports.
for existing proposed fixes.
to find out if the bug was already fixed in the master branch.
(If there are none, check this box anyway).
Related Issues and Possible Duplicates
Related Issues
Possible Duplicates
Description
The Celery website (celeryproject.org) and the Celery documentation website (docs.celeryproject.org) no longer seem to have A DNS records. I've checked this by running
dig celeryproject a
anddig docs.celeryproject.org a
on computers with internet connections in various places in the world, and nowhere seems able to load the website any more.Suggestions
I'm not sure. Has the domain ownership lapsed, or is there just an issue with your DNS provider?
The text was updated successfully, but these errors were encountered: