Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
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.
Hi there,
In case anyone comes across this in the future, as you are able to only see the default Django page, it sounds like you might just have to restart the uwsgi service:
sudo systemctl restart uwsgi
Or if you are using Gunicorn: systemctl restart gunicorn:
Best,
Bobby
It’s possible that uWSGI is still serving the default Django project instead of your custom one.
Run the following command to restart uWSGI and ensure it loads the correct project:
sudo systemctl restart uwsgi
Make sure your firstsite.ini file correctly points to your Django project’s wsgi.py file.
Example of a valid /etc/uwsgi/sites/firstsite.ini:
[uwsgi]
project = firstsite
base = /home/kai
chdir = %(base)/%(project)
home = %(base)/venv
module = firstsite.wsgi:application
socket = /run/uwsgi/%(project).sock
chmod-socket = 664
vacuum = true
master = true
processes = 5
daemonize = /var/log/uwsgi/%(project).log
Make sure chdir points to your actual Django project folder!
If restarting uWSGI didn’t help, check its log for errors:
sudo journalctl -u uwsgi --no-pager | tail -50