Admin page failed logins falling back to site logins


We are using Django 4.2.3 (an upgrade from 3.2.13). Everything is working fine, but when there is a failed login on the /admin page (such as a bad password), the page throws a 500 because it is trying to use our login backend that a normal user would use when accessing the front end website.

Is there a way to make it so /admin logins don’t fall back to our internal backend and throw a reasonable error that the username and password were not correct?

In our settings file, we are specifying the server that should be called for a typical site login on the frontend such as:

    'member': 'http://member.dig.lo',

Edit: It appears this issue exists for us in 3.2.13 as well but I never thought to check :sweat_smile:.