Django migration to postgres - 502 badgateway error in ngnix
19 views
Skip to first unread message
khaleela...@gmail.com
Jul 13, 2016, 8:41:34 AM7/13/16
to Django users
Am migrating to postgres.
My local configuration is runnign without ngnix and my complete migration porcess is working fine in my development machine.
During deployment to production, where the ngnix is configured to run django - I get the error as:
"upstream prematurely closed connection while reading response header from upstream"
This has happened when I do the deployment of postgres settings in the settings. The upstream is pointing to "uwsgi" config.
Not sure, whether its an existing issue.
Can someone help me. Is someone facing the same issue out there?
My local configuration is runnign without ngnix and my complete migration porcess is working fine in my development machine.
During deployment to production, where the ngnix is configured to run django - I get the error as:
"upstream prematurely closed connection while reading response header from upstream"
This has happened when I do the deployment of postgres settings in the settings. The upstream is pointing to "uwsgi" config.
Not sure, whether its an existing issue.
Can someone help me. Is someone facing the same issue out there?
Reply all
Reply to author
Forward
0 new messages