is this? or you put your external ip inside it in the real conf?

ok what i put there?

the ext ip :) [or the domain if you hav eone]

idk i just followed the guide

yes but guide is a guide

is not a "ready for all" tutorial :D

you need to adapt it a bit for your needs

but we are almost there

i adpted things he appointed

with bold

ok

yes but you share a nginx conf with me, where i see server_name server_domain_or_ip;

i have a vhost account

change server_domain_or_ip with external ip address of ec2 please

and reload nginx

yeah sure, i'm just telling you that i don't have experience and don't know what to do

what address?

ipv4? ipv6?

and we are helping you for this reason :)

ipv4

ok

sec

ok mate, did!

now i restart nginx and uwsgi right?

no, just reload nginx. not restart needed

ok, done

ok, now.. we have to check if nginx conf is in the right place

where is your nginx conf for this app? where you put it? i mean path

it's on /etc/nginx/sites-available/

ok

and if you do ls /etc/nginx/sites-available you see it?

with a symlink on /etc/nginx/sites-enabled/

ok

ubuntu@ip-172-31-85-43:~$ ls /etc/nginx/sites-available/ ambiente_er default

it's there

remove the link to default, so we force nginx to serve just ours

ok

your uwsgi.ini file is inside the /etc/uwsgi/sites ... right?

ok removed from both folder, sites-available and sites-enabled

lemme check

ok removed from both folder, sites-available and sites-enabled

not needed, you can remove it from enabled and store the conf inside available so maybe in future can find there. only removed from enabled, in future, is enough

your uwsgi.ini file is inside the /etc/uwsgi/sites ... right?

yes, it's there ubuntu@ip-172-31-85-43:~$ ls /etc/uwsgi/sites/ambiente_er.ini

ok

systemctl reload nginx

done

err_connection_refused

check nginx error logs into var log nginx

https://pastebin.com/GyzaQrBy

it's giving error for you?

for me still same

"welcome to nginx" message

http://52.205.253.147/

"welcome to nginx" message

it's cached, open f12 disable cache and retry

[crit] 14699#14699: *1 connect() to unix:///home/ubuntu/ambiente_er.sock failed (2: No such file or directory)

don't find the uwsgi process so can't proxypass requests

you have to stop the django runserver, not run it in parallel

oh, you're right

and with runserver you call the local

well, i didn't ran runserver

oh

well, i didn't ran runserver

why on port 8000 there is a django ?

i don't know bud, i'm not running that, let me kill the process then

i don't know bud, i'm not running that, let me kill the process then

check why, don't kill

bud

it's not running

look the time

hahaha

that was when i was setting up

i just copied all log file

it's not running

http://52.205.253.147:8000/admin/login/?next=/admin/

so you don't see that?

if i run with python manage.py runserver, the css is loaded

so is not django that's serving this

is not running bud, check the time

2018/10/06 16:25:51 [crit] 14699#14699

16:25

i'm saying another thing. i'm asking why there is a listening django on 8000

i'm not talking about uwsgi

in this way is really hard to help: you need to listen

open the browser on http://52.205.253.147:8000/admin/login/?next=/admin/