Question

Error 503 Service Unavailable

Hi everybody I have a large problem. When i try to go on my website http://liv-in-creation.com/

I see this error "Error 503 Service Unavailable Service Unavailable

Guru Meditation:

XID: 1893582600

Varnish cache server"

So, I have restart Mysql/NGINX/VARNISH but nothing was changed… I have always the same problem. You can find my log here : -rw-r–r-- 1 root root 0 Dec 24 06:52 alternatives.log -rw-r–r-- 1 root root 814 Dec 23 10:10 alternatives.log.1 -rw-r–r-- 1 root root 544 Nov 29 16:16 alternatives.log.2.gz drwxr-x— 2 root adm 4096 Feb 7 06:46 apache2 -rw-r----- 1 root adm 0 Dec 11 06:26 apport.log -rw-r----- 1 root adm 952 Dec 10 15:10 apport.log.1 drwxr-xr-x 2 root root 4096 Dec 24 06:52 apt -rw-r----- 1 syslog adm 3379058 Feb 9 07:36 auth.log -rw-r----- 1 syslog adm 10227657 Feb 7 06:46 auth.log.1 -rw-r----- 1 syslog adm 428861 Feb 1 06:32 auth.log.2.gz -rw-r----- 1 syslog adm 0 Jan 25 06:34 auth.log.3.gz -rw-r----- 1 syslog adm 540365 Jan 17 06:39 auth.log.4.gz -rw-r–r-- 1 root root 6137 Feb 9 05:02 boot.log -rw-r–r-- 1 root root 0 Apr 18 2014 bootstrap.log -rw-rw---- 1 root utmp 18907776 Feb 9 07:36 btmp -rw-rw---- 1 root utmp 39803136 Feb 1 06:32 btmp.1 -rw-r–r-- 1 root root 14275 Feb 9 05:02 cloud-init-output.log -rw-r–r-- 1 syslog adm 648182 Feb 9 05:02 cloud-init.log drwxr-xr-x 2 root root 4096 Apr 12 2014 dist-upgrade -rw-r----- 1 root adm 30745 Feb 9 05:02 dmesg -rw-r----- 1 root adm 30241 Feb 9 04:55 dmesg.0 -rw-r----- 1 root adm 9745 Feb 9 04:55 dmesg.1.gz -rw-r----- 1 root adm 9715 Dec 23 09:56 dmesg.2.gz -rw-r----- 1 root adm 9562 Nov 29 15:44 dmesg.3.gz -rw-r----- 1 root adm 9627 Oct 16 07:27 dmesg.4.gz -rw-r–r-- 1 root root 0 Dec 24 06:52 dpkg.log -rw-r–r-- 1 root root 16698 Dec 23 10:23 dpkg.log.1 -rw-r–r-- 1 root root 2015 Nov 29 16:16 dpkg.log.2.gz -rw-r–r-- 1 root root 3520 Dec 23 10:10 faillog -rw-r–r-- 1 root root 643 Nov 29 16:16 fontconfig.log drwxr-xr-x 2 root root 4096 Apr 17 2014 fsck drwxr-xr-x 3 root root 4096 Apr 17 2014 installer -rw-r----- 1 syslog adm 0 Feb 9 06:44 kern.log -rw-r----- 1 syslog adm 135449 Feb 9 06:44 kern.log.1 -rw-r----- 1 syslog adm 3482 Jan 31 06:25 kern.log.2.gz -rw-r----- 1 syslog adm 99 Jan 19 14:23 kern.log.3.gz -rw-r----- 1 syslog adm 190 Jan 19 06:00 kern.log.4.gz drwxr-xr-x 2 landscape root 4096 Apr 17 2014 landscape -rw-rw-r-- 1 root utmp 32120 Feb 9 06:30 lastlog -rw-r----- 1 syslog adm 0 Jan 15 06:41 mail.err -rw-r----- 1 syslog adm 351 Jan 14 08:08 mail.err.1 -rw-r----- 1 syslog adm 200 Nov 29 15:59 mail.err.2.gz -rw-r----- 1 syslog adm 47923 Feb 9 07:32 mail.log -rw-r----- 1 syslog adm 180415 Feb 7 06:31 mail.log.1 -rw-r----- 1 syslog adm 4366 Feb 1 06:15 mail.log.2.gz -rw-r----- 1 syslog adm 0 Jan 19 09:54 mail.log.3.gz -rw-r----- 1 syslog adm 942 Jan 14 08:22 mail.log.4.gz drwxr-s— 2 mysql adm 4096 Feb 9 06:44 mysql -rw-r----- 1 mysql adm 0 Jul 28 2015 mysql.err -rw-r----- 1 mysql adm 0 Feb 9 06:44 mysql.log -rw-r----- 1 mysql adm 20 Feb 8 06:26 mysql.log.1.gz -rw-r----- 1 mysql adm 20 Feb 7 06:46 mysql.log.2.gz -rw-r----- 1 mysql adm 20 Feb 6 06:29 mysql.log.3.gz -rw-r----- 1 mysql adm 20 Feb 5 06:50 mysql.log.4.gz -rw-r----- 1 mysql adm 20 Feb 4 06:40 mysql.log.5.gz -rw-r----- 1 mysql adm 20 Feb 3 06:45 mysql.log.6.gz -rw-r----- 1 mysql adm 20 Feb 2 06:50 mysql.log.7.gz drwxr-x— 2 www-data adm 4096 Dec 27 06:33 nginx -rw-r----- 1 syslog adm 1451 Feb 9 07:32 syslog -rw-r----- 1 syslog adm 182682 Feb 9 06:44 syslog.1 -rw-r----- 1 syslog adm 2920 Feb 8 06:26 syslog.2.gz -rw-r----- 1 syslog adm 3087 Feb 7 06:39 syslog.3.gz -rw-r----- 1 syslog adm 2959 Feb 6 06:25 syslog.4.gz -rw-r----- 1 syslog adm 3518 Feb 5 06:40 syslog.5.gz -rw-r----- 1 syslog adm 3210 Feb 4 06:39 syslog.6.gz -rw-r----- 1 syslog adm 2973 Feb 3 06:39 syslog.7.gz -rw-r–r-- 1 root root 149250 Feb 9 05:02 udev drwxr-xr-x 2 root root 4096 Jul 28 2015 unattended-upgrades drwxr-xr-x 2 root root 4096 Feb 9 04:55 upstart drwxr-x— 2 varnishlog varnishlog 4096 Mar 23 2015 varnish -rw-rw-r-- 1 root utmp 18816 Feb 9 06:48 wtmp -rw-rw-r-- 1 root utmp 1536 Jan 19 08:11 wtmp.1

But i don’t know many things about server… I’m a little bit lost.

Can you help me please. Thank you very much.

Show comments

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This question was answered by @henrilepic:

It looks like your server have a varnish process running with no backend connexion to your websites: the varnish service has binded the port 80 and your nginx is then unable to bind it.

If your not considering to set and use varnish you may try the following :

  • log in terminal on your server as root then #service varnish stop #/usr/bin/nginx

If you want to use varnish, you have to set your nginx to listen to the right port (by default the port 6082). This way varnish will serve page with port 80 using your websites on port 6082 in the backend.

I hope this will help…

View the original comment