Website is down #44
Comments
|
credit card issue |
|
Doesn't seem to be a domain issue as docs.celeryproject.org seems to be working fine. Anything we can help with? |
|
its rackspace needed a new credit card |
|
We need to design and move our website to Github Pages anyway in my opinion. |
|
I wanted to learn this but apparently your page is still down, what is happening? |
|
@Ryuuji159 The documentation is still up at https://docs.celeryproject.org/en/stable/ Only the project homepage is down. |
|
Even though users who Google about a bit can eventually find the docs, this does result in a lot of broken links from other people's articles and projects that pointed to http://celeryproject.org … even Celery's own GitHub org page:
Perhaps until the new site is ready, you might consider redirecting the project homepage to the docs site or the main GitHub repo? (It looks like celeryproject.org's DNS is at A Small Orange; their KB has info on setting up a redirect.) |
|
Bump. Came to report this and say what @medmunds already said; the domain should at least redirect to the docs site until there's something else for it to point at. |
we already pointed the doc site as website in github. but a real redirect need access to domain |
|
So what do you guys need to fix this? |
|
I need access to the DNS anyway. |
I tried but didn't get. I tried to recover racksapce account but with no luck. |
It looks like the DNS for celeryproject.org is using nameservers managed by A Small Orange (not directly at Rackspace). You might try to recover the account from them: https://help.asmallorange.com/ % dig +short -t NS celeryproject.org
ns1.asmallorange.com.
ns2.asmallorange.com.(A Small Orange appears to be built on services from Rackspace and eNom, but I'm guessing the celeryproject.org domain registration and DNS were through A Small Orange.) |
|
@auvipy Can you take care of that? |
I can try |
|
It looks like https://docs.celeryproject.org/en/stable/ went down again yesterday. |
we are goin to configure new domains for the project |
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
Ping @auvipy @fireantology @ask
The text was updated successfully, but these errors were encountered: