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 4613394
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T01:32:32+00:00 2026-05-22T01:32:32+00:00

I just upgraded from django 1.2.4 to 1.3. I’m using nginx in conjunction with

  • 0

I just upgraded from django 1.2.4 to 1.3.

I’m using nginx in conjunction with fastcgi and for some reason every time when I access a page I get this error:

Unhandled Exception

An unhandled exception was thrown by the application.

Any ideas what the problem might be?

  • 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-05-22T01:32:32+00:00Added an answer on May 22, 2026 at 1:32 am

    To fix it I added this class (that practically doesn’t do anything) in the : /usr/local/lib/python2.6/dist-packages/django/middleware/http.py

    class SetRemoteAddrFromForwardedFor(object):
        """
        This middleware has been removed; see the Django 1.1 release notes for
        details.
    
        It previously set REMOTE_ADDR based on HTTP_X_FORWARDED_FOR. However, after
        investiagtion, it turns out this is impossible to do in a general manner:
        different proxies treat the X-Forwarded-For header differently. Thus, a
        built-in middleware can lead to application-level security problems, and so
        this was removed in Django 1.1
    
        """
        def __init__(self):
            import warnings
            warnings.warn("SetRemoteAddrFromForwardedFor has been removed. "
                          "See the Django 1.1 release notes for details.",
                          category=DeprecationWarning)
            raise MiddlewareNotUsed()
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I just upgraded from tomcat 6.0.29 to 7.0.25 using native apr. Tomcat has crashed
We just upgraded some maven dependencies, that triggered an update of Jackson from 1.7.x
I am using visual studio 2008 on vista business. We just recently upgraded from
I have just upgraded from php 5.1 to 5.3 and had previously been using
I've just upgraded Django from 1.2.3 to 1.4 and realized that django.middleware.csrf.CsrfResponseMiddleware is depricated.
I have just upgraded from EF 4.0.0 to EF 4.3.1. I am using Visual
I just upgraded from SnowLeapord to Lion and now cannot create virtualenvs. I understand
I just upgraded from VS2008 to VS2010. In the process, I allowed it to
I just upgraded from Rails 3.0.3 to 3.2.1. The upgrade went smoothly on my
I've just upgraded from MRI-1.8.7 to MRI-1.9.1 and heard about this lighthouse ticket which

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.