Wait, wait
From which file the second image you shared came from in the previous post ? the one with colored text
i have found the file where the server take the wellcome message, so i have edited to send a message to the visitors of the site… cause it’s lot of day now are offline
path: /var/www/html
edit: vim index.nginx-debian.html
:wq! to save
that’s my log:
i have opened with vim
vim /etc/nginx/sites-available/default - colored text
after
vim /etc/nginx/sites-available/peertube - not colored only black text
the one with colored text come from vim /etc/nginx/sites-available/default that have colored text
let’s try removing this default file (but make a copy though, in case of):
sudo mv /etc/nginx/sites-enabled/default ~/default.bak
Then recheck the configuration with nginx -t. If no error, reload or restart the nginx service
ok after reboot something change
OK, let’s restore the default (but I tend to think that’s the culprit because i think it contains ref to peertube.it)
sudo mv ~/default.bak /etc/nginx/sites-enabled/default
before restore and after restore: nginx -t
we need to make the default nginx sites-enabled the peertube file instead of the default original one, there is some command to do to make the peertube file the default one?
i think we have to check the nginx config … any help?
OK, you did modify the content of default in a time, isn’t it ?
that it’s the default file opened with vim, what’s happen if instead of
root /var/www/html
replace it with
root /var/www/peertube
did you think that’s can a good solution?
what’s the « default » file you refer to? If you mean the default site-enabled file bundled with Nginx, you can discard it.
i mean that file /etc/nginx/sites-enabled/default cause if i remove it server give error 502 bad gateway
Maybe you may envisage to restart from scratch 
I think that in some way, you modify the default content and that leads to the actual situation.
i don’t know … 
i try to modify the /etc/nginx/sites-available/default with vim
nothing i have tested different config but nothing i get ever same error 503 or worst
now i give up with normal install i will try with cloudron
Cloudron Wins!
i have solved by installing cloudron and in 5 min i get my peertube instance back.
so i think the normal install procedure have to be done only by very high grade expert server side users.
Good news!
1 « J'aime »