Yes, the stack trace is from python, but I only get the issue using
nginx and uwsgi with the same django code.
As to your question, I have 2 different deployments of this app with
nginx and uwsgi. One is using django1.9 and python 2.7 and a single
uwsgi config and the second is using django2.0 and
Given that the stack trace is from Python, it’s not an nginx configuration
issue. Are you reverse proxying from nginx multiple uwsgi backgrounds that have
different configuration?
Sent from my iPhone
> On Jan 5, 2019, at 13:01, Larry Martell wrote:
>
> I am having an odd interment django prob
I am having an odd interment django problem. I have an app which is
deployed at 30 different sites, some with apache and wsgi and some
with nginx and uwsgi. At only the nginx/uwsgi sites and only
intermittently, users will get the error No module named
context_processors.
I am only posting it here
