Adding openid_connect to INSTALLED_APPS causes login view to fail about django-allauth HOT 3 CLOSED

There is no reason why allauth would go looking for a provider called accounts without that being configured somehow, unless the project's URL routing somehow mistakenly interprets the accounts in your /en/accounts/login as a provider ID. I would recommend you first use standard URL routing (e.g. don't auto prefix /en/) and then figure out why things start breaking when you gradually expand from there...

from django-allauth.

Closing -- feel free to reopen if you have a reproducible scenario with an uncustomized allauth.

from django-allauth.

It's redirected to /en as it's a multilingual site. No site exists at /.
'accounts' isn't configured anywhere other than being a prefix for the allauth urls.
It's only on the login view, and only when OIDC is added to INSTALLED_APPS that this issue arises with or without an OIDC provider defined.

Your suggestion regarding the urls did lead me to find a duplicate path for allauth.urls though:

urlpatterns = urlpatterns + i18n_patterns(
    ...
    re_path(r'^accounts/', include('allauth.urls')),
    ...
    re_path(r'', include('allauth.urls')),
    ...
)

When I take out the second, the error goes away. It was there for some historic reason I can only guess.

I couldn't track what calls with provider='accounts' in the end. From searching and stepping through the code, it comes from the get_providers & provider_login_url templatetags, but these don't even get called when the error gets thrown. I can even see the error in the console when starting the server.

Anyway, thanks for the help, much appreciated!

from django-allauth.