Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9129191
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 17, 20262026-06-17T07:41:21+00:00 2026-06-17T07:41:21+00:00

So I upgraded from django 1.3 to 1.4, everything went smoothly. However a few

  • 0

So I upgraded from django 1.3 to 1.4, everything went smoothly. However a few users just get an Internal Server Error, thrown by nginx, usually when the server has crashed.

Investigating this showed that it was problems with cookies. The error in the log was:

ImproperlyConfigured: Error importing authentication backend
  site.app.backends.EmailModelBackend: "No module named site.app.backends"

This is because during the upgrade I reorganized my project, and this particular backend is now at app.backends rather than site.app.backends. Clearly this information is hard-coded into the auth cookie, which is causing the problem.

Is there any way to sort this out short of emailing users and telling them to clear their cookies?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-17T07:41:23+00:00Added an answer on June 17, 2026 at 7:41 am

    If you are using the default database-backed sessions, then the reference to the old backend is stored in the django_session table, and the user’s cookie is just a reference to the row in the database. In that case, you could prevent the errors by deleting all the session data from your database.

    Think carefully before you do this. You might not want to delete all your session data — for example, it will log out all of your users.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I just upgraded from django 1.2.4 to 1.3. I'm using nginx in conjunction with
I upgraded to django 1.2 and I now get this error message which looks
I've just upgraded Django from 1.2.3 to 1.4 and realized that django.middleware.csrf.CsrfResponseMiddleware is depricated.
I upgraded from SQl server 05 to 08 and had a few issues. After
We have recently upgraded from SQL Server 2005 to SQL Server 2008 (R2, SP1).
I just upgraded from SnowLeapord to Lion and now cannot create virtualenvs. I understand
I've just upgraded from MRI-1.8.7 to MRI-1.9.1 and heard about this lighthouse ticket which
I have recently upgraded from websphere 5.1.2 to websphere 6.1 server. I had some
I just upgraded from VS2008 to VS2010. In the process, I allowed it to
I recently upgraded from Vista/32 to Win7/64. On my old machine, everything was working

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.