Issue #9 invalid

Error 500 on Heroku deployed app, while everything works fine on local instance

Anonymous created an issue

Hi,

I am using Heroku and Django for my Web Application.

I'm trying to use the features lockdown to control the access to my app. After having followed the steps to set lockedown, everything seems to work fine on my local environment ( a password is required)

But once, I push the modifications of settings.py on Heroku remote, I get an error 500.

Here are the logs :

2014-04-08T05:44:02.963770+00:00 app[web.1]: 2014-04-08 00:44:02 [7] [ERROR] Error handling request
2014-04-08T05:44:02.963770+00:00 app[web.1]: Traceback (most recent call last):
2014-04-08T05:44:02.963770+00:00 app[web.1]:   File "/app/.heroku/python/lib/python2.7/site-packages/gunicorn/workers/sync.py", line 126, in handle_request
2014-04-08T05:44:02.963770+00:00 app[web.1]:     respiter = self.wsgi(environ, resp.start_response)
2014-04-08T05:44:02.963770+00:00 app[web.1]:   File "/app/.heroku/python/lib/python2.7/site-packages/django/core/handlers/wsgi.py", line 236, in __call__
2014-04-08T05:44:02.963770+00:00 app[web.1]:     self.load_middleware()
2014-04-08T05:44:02.963770+00:00 app[web.1]:   File "/app/.heroku/python/lib/python2.7/site-packages/django/core/handlers/base.py", line 53, in load_middleware
2014-04-08T05:44:02.963770+00:00 app[web.1]:     raise exceptions.ImproperlyConfigured('Error importing middleware %s: "%s"' % (mw_module, e))
2014-04-08T05:44:02.963770+00:00 app[web.1]: ImproperlyConfigured: Error importing middleware lockdown.middleware: "No module named lockdown.middleware"
2014-04-08T05:44:02.966439+00:00 heroku[router]: at=info method=GET path=/ host=wheeli-development.herokuapp.com request_id=bf2170a8-da9a-44cb-9f47-8cc6b197b76e fwd="74.71.57.202" dyno=web.1 connect=1ms service=6ms status=500 bytes=238

Comments (1)

  1. Log in to comment