# Toegang verloren tot Discourse login (geen inloggegevens), oorspronkelijke domein verloren - probeert nu te migreren naar nieuwe DO droplet
**URL:** https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669
**Category:** Support
**Created:** [11 januari 2025 om 18:29 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669 "2025-01-11T18:29:41Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [11 januari 2025 om 18:29 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/1 "2025-01-11T18:29:41Z")
Is anyone familiar with this problem?
I’ve consulted with:
> **[Migrate Discourse Forum to Another Server - Gulshan Kumar](https://www.gulshankumar.net/discourse-forum-server-migration/)**
>
> Do you wish to migrate Discourse to a new Cloud Server Instance? Follow this ultimate guide.
> [@Discourse lost the ability to login for all accounts](https://meta.discourse.org/t/discourse-lost-the-ability-to-login-for-all-accounts/51775):
>
> I’m using Digital Ocean droplet to host Discourse(last version) with Nginx+Let’s Encrypt SSL in front. Yesterday when I was working to enable LinkedIn OAuth login. I’d enabled FORCE\_HTTPS to try if it will make OAuth login work but I lost the ability to login from to all accounts. After I’d tried many advice’s from the community nothing worked. So I restored my previous droplet snapshot to my working copy. Then I started by enabling FORCE\_HTTPS to test if anything will broke. Everything worked…
I’m not familiar with how I implement solution in 2nd link without access to old domain. Anyone know the workaround? Thanks!
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [11 januari 2025 om 19:10 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/2 "2025-01-11T19:10:40Z")
I don’t know what “second link” you’re talking about.
Try ` /u/admin-login`
And also `rake admin:create` (inside the container).
> [@Geroy](#):
>
> I’m not familiar with how I implement solution in 2nd link without access to old domain.
Is the new site up somewhere? Can you share that?
---
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [20 januari 2025 om 18:54 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/3 "2025-01-20T18:54:58Z")
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
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [20 januari 2025 om 23:04 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/4 "2025-01-20T23:04:28Z")
If the site is up Add /u/admin-login to your site url and get an email link to log in
> [@Geroy](#):
>
> But the discourse forums are not displaying inside the droplet docker container
I don’t understand what this means.
---
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [21 januari 2025 om 05:18 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/5 "2025-01-21T05:18:15Z")
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.
---
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [21 januari 2025 om 05:35 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/6 "2025-01-21T05:35:08Z")
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. :\
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [21 januari 2025 om 15:24 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/7 "2025-01-21T15:24:26Z")
Do you have nginx in front of discourse as in the link in the OP or is this a [standard install](https://meta.discourse.org/t/142537?silent=true)?
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.
---
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [21 januari 2025 om 15:35 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/8 "2025-01-21T15:35:20Z")
It’s [forum.domain.com](http://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.
---
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [21 januari 2025 om 17:49 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/9 "2025-01-21T17:49:24Z")
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.
---
### Author:  [@Geroy](https://meta.discourse.org/u/Geroy)
#### Post date: [21 januari 2025 om 19:33 UTC](https://meta.discourse.org/t/lost-access-to-discourse-login-no-credentials-lost-original-domain-now-trying-to-migrate-to-new-do-droplet/346669/11 "2025-01-21T19:33:07Z")
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.