The default config/template of the 3.3.x branch wont result in a working setup.
There is an issue with nginx not being able to proxy to the django container using uwsgi:
Since i was able to connect to django container directly from the host using the mentioned ip and port in error log, i first checked the nginx config and replacing uwsgi_pass $upstream;with proxy_pass http://$upstream;fixed the issue.
Tho i bet there was a reason to use uwsgi.
The main culprit is in the ./src/uwsgi.ini. the 3.3.x one uses http_socket instead of socket and this results in nginx not being able to connect using uwsgi_pass.
The default config/template of the 3.3.x branch wont result in a working setup. There is an issue with nginx not being able to proxy to the django container using uwsgi:
Since i was able to connect to django container directly from the host using the mentioned ip and port in error log, i first checked the nginx config and replacing
uwsgi_pass $upstream;
withproxy_pass http://$upstream;
fixed the issue. Tho i bet there was a reason to use uwsgi.Since the master/4.X Branch worked fine i checked the latest commits and found: https://github.com/GeoNode/geonode-project/commit/a74f55ea4b00d9bcf4291a7ddbb75ceed2071c2c . This one wasn't merged into the 3.3.X branch so i applied the changes to
geonode.conf
anduwsgi.ini
manually and this fixed the issue in 3.3.x as well.The main culprit is in the
./src/uwsgi.ini
. the 3.3.x one useshttp_socket
instead ofsocket
and this results in nginx not being able to connect usinguwsgi_pass
.