# Locked out of Development Instance
**URL:** https://forum.djangoproject.com/t/locked-out-of-development-instance/41041
**Category:** Mystery Errors
**Created:** [May 22, 2025, 10:53am UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041 "2025-05-22T10:53:16Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@onyeibo](https://forum.djangoproject.com/u/onyeibo)
#### Post date: [May 22, 2025, 10:53am UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041/1 "2025-05-22T10:53:16Z")
I am unable to log into an instance of a Django app under development as a SuperUser. I have changed password through `./manage.py changepassword` successfully. I have also changed password via the running instance of the app (it has **password recovery** all set up and functional).
Yet, on the login page, the authentication still fails. What could be the cause?
More …
I have tried creating a fresh superuser with `./manage.py createsuperuser`. The newly created account also fails to login the page. I did not tamper with the view. What is going on? How do I troubleshoot this?
Note:
I recently migrated from Django 5.1 to 5.2
---
### Author:  [@Jdsleppy](https://forum.djangoproject.com/u/Jdsleppy)
#### Post date: [May 22, 2025, 1:46pm UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041/2 "2025-05-22T13:46:36Z")
Does auth fail with server side errors, or do you get a Permission Denied 403 or similar? If server error, is there any stack trace you can share?
Are you using Django’s built-in auth backend, or something 3rd party (allauth?) or custom?
Are you trying to log in at the Django admin or at your own login page? Can you log in at the Django admin and THEN visit your site?
---
### Author:  [@onyeibo](https://forum.djangoproject.com/u/onyeibo)
#### Post date: [May 22, 2025, 2:09pm UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041/3 "2025-05-22T14:09:05Z")
> [@Jdsleppy](#):
>
> Can you log in at the Django admin and THEN visit your site?
That worked. Thanks
So then the issue is with my login implementation. I am using `allauth`. The only error message I get is from` form.errors` (“`password and username doesn't match`”). The view that is rendering is `LoginView` as per:
`from allauth.account.views import LoginView`
Whereas, it is the failing password/user pair that worked for the admin page
---
### Author:  [@onyeibo](https://forum.djangoproject.com/u/onyeibo)
#### Post date: [May 22, 2025, 2:10pm UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041/4 "2025-05-22T14:10:48Z")
Can a reset in migrations affect authtentication? Is it possible that resetting migrations can affect authenticcation?
---
### Author:  [@Jdsleppy](https://forum.djangoproject.com/u/Jdsleppy)
#### Post date: [May 22, 2025, 2:35pm UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041/5 "2025-05-22T14:35:18Z")
I don’t think migrations would be an issue. Since you recently updated Django, did you check that your current version of allauth supports Django 5.2? Check the allauth changelog to see if there are any interesting notes.
---
### Author:  [@onyeibo](https://forum.djangoproject.com/u/onyeibo)
#### Post date: [May 22, 2025, 5:57pm UTC](https://forum.djangoproject.com/t/locked-out-of-development-instance/41041/6 "2025-05-22T17:57:51Z")
I decided to update allauth instead. It was at 65.3.x
After the update the following showed up:
```auto
System check identified some issues:
WARNINGS:
?: settings.ACCOUNT_EMAIL_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'password1*']
?: settings.ACCOUNT_SIGNUP_PASSWORD_ENTER_TWICE is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'password1*']
?: settings.ACCOUNT_USERNAME_REQUIRED is deprecated, use: settings.ACCOUNT_SIGNUP_FIELDS = ['email*', 'password1*']
```
I also found out that my login dilemma showed up from version [65.5.x](https://allauth.org/news/2025/03/django-allauth-65.5.0-released/). Whereas, my update brought in 65.8.1
I now understand what messed up the login. I had updated a module that pulled in newer packages (except allauth). I have applied the recommended fixes as per the error message above.
The login is working again. Thank you very much