Is anyone familiar with this problem?
I’ve consulted with:
I’m not familiar with how I implement solution in 2nd link without access to old domain. Anyone know the workaround? Thanks!
AI-generated summary
Geroy is struggling to regain access to a Discourse forum after losing the original domain and attempting to migrate to a new DigitalOcean droplet. Despite consulting guides like this one, they can’t implement fixes without access to the old domain. Attempts to use /u/admin-login and rake admin:create fail because the forum doesn’t display — instead, users see an ERR_TOO_MANY_REDIRECTS error. Geroy has re-registered the original domain, updated DNS via Cloudflare, and rebuilt the app, but the forum still won’t load. pfaffman suggests checking if nginx is misconfigured or if the server is rate-limited due to prior DNS mismatches. Geroy confirms the setup was working for months before the domain was hijacked by spam. They suspect an SSO misconfiguration may be causing the redirect loop, though user data should remain locally in the droplet. Additionally, Geroy notes that discourse-doctor reports an outdated Ruby version blocking bundle install, which may be contributing to the issue. The core problem remains unresolved: the forum fails to render, and admin access is inaccessible.
I don’t know what “second link” you’re talking about.
Try /u/admin-login
And also rake admin:create (inside the container).
Is the new site up somewhere? Can you share that?
Hi sorry for late reply.
New site as well as old site are up. But the discourse forums are not displaying inside the droplet docker container. So I can’t bring up /u/admin-login
If the site is up Add /u/admin-login to your site url and get an email link to log in
I don’t understand what this means.
The website is loading with an "ERR_TOO_MANY_REDIRECTS " error. I’m not sure if this is the underlying issue or just a symptom.
The error with the website is not related to networking/server-related issues, running “apt-update” or checking the network configuration file (I tried all this earlier) will not help to fix the website issue. The discourse forum just doesn’t display.
I’ve managed to reregister the original domain, I’ve changed back the settings in app.yml, fixed DNS records in CF, etc., the discourse forum is still not even displaying on original domain. :\
Do you have nginx in front of discourse as in the link in the OP or is this a standard install?
My guess is that you did a bunch of rebuilds with the domain you want while the DNS for that domain didn’t resolve to the server and you’re now rate limited for a week. It’s hard to tell, though.
If you have an nginx in front of Discourse, then the issue is likely with it not doing the right thing, or it using one hostname while Discourse is doing another.
It’s forum.domain.com and the discourse install is on forum. The discourse forum functioned and ran properly for months and months, had user input, etc. Then the original domain got taken over by Chinese spam.
I read elsewhere that an SSO configuration could be creating a redirect loop, and I AM getting the too many redirects error. But user data should be in the droplet in the discourse setup, not stored elsewhere. I don’t know why there’d be a user sign-on issue.
Would an out of date ruby install be holding it up?
I’m going through the discourse-doctor debug file and it ends with an out of date ruby holding up the discourse and gem install bundle. There’s a couple errors beforehand as well but they seem not as important.