English (change) 
La oss ta en rask titt på vår Nginx server og nettsted feil og få tilgang til loggene, og hvor du finner dem.
Du har ett par Nginx logger hele serveren og en annen for hvert nettsted, med mindre du utelatt dem. Feilen logger gjøre akkurat det, logger eventuelle feil. Tilgangen loggene viser hva web-elementer har blitt løst ved IP-adresse og når.
De som fulgte viser flere nettsteder og blogger med Virtual Hosts kartlagt plasseringen av stokkene på hvert sted eller blogger virtuelle host filen eller, hvis du buntet hvert område konfigurasjon i nginx.conf fil, plasseringen til filene er angitt der.
Her er en påminnelse allikevel.
I 20 kopier / lim trinn .. fra null til helten, tomme boksen til søt-og Linux-server.
Bla ned for full serie indeksen.
Så hei, shed delte & viva virtuelt! Håper det hjelper. The_guv
Å liste dem: --
ls -l /usr/local/nginx/logs
Or to open them:-
sudo nano /usr/local/nginx/logs/error.log
.. substituting error.log for access.log as appropriate.
Or if you installed Nginx using the package manager, rather than compiling from source as is recommended in the VPS Bible, they're here:-
sudo nano /etc/nginx/logs
sudo nano /home/public_html/someSite.com/log/access.log
And the error page:-
sudo nano /home/public_html/someSite.com/log/error.log
In the case of the error log, hopefully it is indeed empty. With the access log, maybe it's just too darn big and is taking a long time to open. If you really want to look at it, be patient. Else delete it and add a new, empty one:-
sudo rm /home/public_html/someSite.com/log/access.log && sudo nano /home/public_html/someSite.com/log/access.log
.. saving the empty file.
Serve multi sites & blogs on a budget .. at the fastest possible speed .. with the least downtime .. in the most secure environment .. and future-proofed for easy admin.
That's what the VPS Bible is about, stepped out in simple copy & paste guides.
From high traffic WordPress blogs to startup web hosts, here's what you need.
Set it up? Click here for the 21 part follow-up .. V-P-S Admi Å liste dem: --
ls -l /usr/local/nginx/logs
Or to open them:-
sudo nano /usr/local/nginx/logs/error.log
.. substituting error.log for access.log as appropriate.
Or if you installed Nginx using the package manager, rather than compiling from source as is recommended in the VPS Bible, they're here:-
sudo nano /etc/nginx/logs
sudo nano /home/public_html/someSite.com/log/access.log
And the error page:-
sudo nano /home/public_html/someSite.com/log/error.log
In the case of the error log, hopefully it is indeed empty. With the access log, maybe it's just too darn big and is taking a long time to open. If you really want to look at it, be patient. Else delete it and add a new, empty one:-
sudo rm /home/public_html/someSite.com/log/access.log && sudo nano /home/public_html/someSite.com/log/access.log
.. saving the empty file.
Serve multi sites & blogs on a budget .. at the fastest possible speed .. with the least downtime .. in the most secure environment .. and future-proofed for easy admin.
That's what the VPS Bible is about, stepped out in simple copy & paste guides.
From high traffic WordPress blogs to startup web hosts, here's what you need.
Set it up? Click here for the 21 part follow-up .. V-P-S Admin
THE_GUV NEEDS YOU!!
.. to improve this post ..
Please clue me in. What's wrong or missing?
Or, hey, just pile on the praise ;) Ah, yup, and fix a feed, fella.
Or link the page to your social network!
thank you, thanx, tx, ta, t, tsst, twaddle, cheek, cheers, cheerio