Doesnt work on public IP - uWSGI, Nginx

Using Django Deployment
21

I thought Nginx was easy :frowning:

I use that file to make uwsgi run at startup system, with commands

uwsgi --ini my_project.ini
sudo ln -s /home/fornakter/django/my_project.ini /home/fornakter/django/venv/vassals/

Maybe is better for me to start again with Gunicorn?

22

Letā€™s take a step back here.

Where are you getting these commands and files from that you are trying to use?

Are you trying to combine information from multiple sources? (Thatā€™s generally a really bad idea for something like this. Find one comprehensive source and use it exclusively. Do not go looking for information anywhere else unless itā€™s explicitly intended to expand on or enhance your primary source.)

Thatā€™s entirely up to you.

But my recommendation at first - regardless of the uwsgi/gunicorn choice - is to get this working with a TCP socket before trying to get it working with a domain socket.

Nginx is easy. Uwsgi is actually fairly easy. Itā€™s getting all these different parts working together that can be difficultā€¦

23

Iā€™ll just provide a link to the course I used

24

Ok, so reading through this, it appears to be laid out in a sequence of steps.

Iā€™m hoping you worked through these steps in the order presented.

At which step did things stop working?

25

Not really that au fait with uWSGI, but isnā€™t the simplest way to check it is running to connect to it directly, rather than through an intermediate web server, ie:

http://127.0.0.1:9090

?

26

Except that in the configuration shown, uwsgi isnā€™t listening on a tcp port. Itā€™s connecting to a unix domain socket.

27

Again, outside my experience really, but canā€™t you telnet to the socket, or something!?

28

As i sad on top - Django doesnt work on public IP
I want to start server with django website. Everything works on local IP, but on public works only Nginx.

29

If you run the uWSGI service connecting via a tcp port, you can connect to it directly, rather than via Nginx, ie http://127.0.0.1:9090.

If you are running it to connect via a Unix socket, then I donā€™t know how to connect to that, but I am sure it is possible.

Trying to connect to the uWSGI service directly confirms that the uWSGI service is running, etc, so that you can perhaps narrow your problem down to a Nginx, or other, configuration issue.

30

No, it is not. At least not directly.