You bring your web app in a
- GitHub repo
- App Platform handles deployments and builds
- DNS, HTTPS, CDN, DDoS Mitigation, Vertical Scaling, Horizontal Scaling, and more.
Adding New Relic to Upstart config in Django one-click install causing 502 Error
Here is my Gunicorn config, with the changes I made in bold. After saving this and doing a sudo service gunicorn restart, I received a 502 error and my website is down. I’m hoping someone can help or tell me what I’m doing wrong, I have verified that all the new relic related paths included below are correct.
description "Gunicorn daemon for Django project" start on (local-filesystems and net-device-up IFACE=eth0) stop on runlevel [!12345] # If the process quits unexpectedly trigger a respawn respawn setuid django setgid django chdir /home/django env NEW_RELIC_CONFIG_FILE=/home/django/django/dealr/newrelic.ini exec /local/bin/newrelic-admin run-program gunicorn \ --name=django_project \ --pythonpath=django_project \ --bind=0.0.0.0:9000 \ --config /etc/gunicorn.d/gunicorn.py \ django_project.wsgi:application
I was trying to follow this thread.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×