Answers.Body: <p>Okay, my next stackexchange question will be "Where is the dunce cap?" because I could use one. My problem was not actually a problem, and Lindsey D was exactly right: I was just going to <code>mysite.com</code>, not to <code>mysite.com/admin</code>.</p>
  
  <p>And I see now that that was clearly stated in the install instructions, a tab that I was referring to over the course of the whole afternoon!</p>
  
  <p>Thanks, Lindsey, my morning just opened up. And to the dev of posterity who finds his way to this question and answer: I know it hurts.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-07-17T07:42:19.037Z
Answers.Text: Thanks. Our server started returning a 503 and I needed this tip to find out the cause, thank you! ;-)
Answers.UserDisplayName: Simon East
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2016-07-20T14:29:50.133Z
Answers.LastActivityDate: 2016-07-20T14:29:50.133Z
Answers.UserDisplayName: Erik G
Body: <p>I've spent all of today trying to configure a server block that will let me install Craft 2.62797 on a Digital Ocean droplet running Ubuntu 14.04 with NGINX and PHP 7.</p>
  
  <p>After uploading the craft directory and a public directory with the index.php file, a visit to my site gets the</p>
  
  <p><code>**Service Unavailable** Our site is temporarily unavailable. Please try again later.</code></p>
  
  <p>error.</p>
  
  <p>At first I was using the server block recommended by Brad Bell in <a href="https://craftcms.stackexchange.com/questions/961/what-is-the-recommended-nginx-configuration-for-craft">this post.</a></p>
  
  <p>Unfortunately that setup uses 127.0.0.1:9000 for a socket, and none of the other sites on our droplet uses a TCP socket -- they all use this chunk for fastcgi</p>
  
  <p><code>location ~ \.php$ {
          fastcgi_split_path_info ^(.+\.php)(/.+)$;
          fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
          fastcgi_index index.php;
          include fastcgi_params;
     }
  </code></p>
  
  <p>So I tried dropping that in, no dice. Here's some of the debug info from the site's error log. I think this is where it all goes wrong:</p>
  
  <p><code>2016/07/19 16:50:08 [debug] 4362#4362: *18 connect to unix:/var/run/php/php7.0-fpm.sock, fd:23 #20
  2016/07/19 16:50:08 [debug] 4362#4362: *18 connected
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http run request: "/index.php?"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream check client, write event:1, "/index.php"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream recv(): -1 (11: Resource temporarily unavailable)
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream request: "/index.php?"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream dummy handler
  2016/07/19 16:50:08 [debug] 4362#4362: *18 post event 00007FB15402C770
  2016/07/19 16:50:08 [debug] 4362#4362: *18 post event 00007FB15403E780
  2016/07/19 16:50:08 [debug] 4362#4362: *18 delete posted event 00007FB15402C770
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream request: "/index.php?"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http fastcgi parser: 0
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http fastcgi header: "Status: 503 Service Unavailable"
  </code></p>
  
  <p>(I edited it for brevity, don't think I clipped out anything relevant).</p>
  
  <p>For what it's worth, I tried editing PHP's www.conf settings, to allow for listening on 127.0.0.1 and port 9000, as per <a href="https://stackoverflow.com/questions/21524373/nginx-connect-failed-111-connection-refused-while-connecting-to-upstream">this post</a>. I knew this would break all the other sites, but I wanted to see if I could get it working -- still got a bad gateway error. (Possible that I hadn't restarted PHP after that change, though.)</p>
  
  <p>The bizarre thing about all this is that I have a working Craft CMS install on this same droplet. I tried duplicating its server block, which was auto-generated by Laravel Forge, but that netted me the same error message <em>and</em> didn't log anything to the error log.</p>
  
  <p>Anyway, that's about all I know -- I'm sure I'm leaving something out, but I'm a bit frayed by the debugging process. Would be grateful for any advice.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-19T22:09:24.960Z
Comments.Text: Have you tried going to `yoursite.com/admin`? That "Service Unavailable" message on the front-end could mean many things. You won't know for certain until you ping the back-end.
Comments.UserDisplayName: Lindsey D
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-19T22:20:03.207Z
Comments.Text: When you get the 503, are you getting a square box in the center with that message or the standard nginx-styled  503 message? Craft also throws up a 503 if MySQL goes down.... might be worth a restart.
Comments.UserDisplayName: RitterKnight
Tags: <php>
Title: 503 Response on fresh install, FastCGI possible culprit
ThreadText: # 503 Response on fresh install, FastCGI possible culprit
  
  (Asked by: username_0 on 2016-07-19)
  
  I've spent all of today trying to configure a server block that will let me install Craft 2.62797 on a Digital Ocean droplet running Ubuntu 14.04 with NGINX and PHP 7.
  
  After uploading the craft directory and a public directory with the index.php file, a visit to my site gets the
  
  `**Service Unavailable** Our site is temporarily unavailable. Please try again later.`
  
  error.
  
  At first I was using the server block recommended by Brad Bell in [this post.](https://craftcms.stackexchange.com/questions/961/what-is-the-recommended-nginx-configuration-for-craft)
  
  Unfortunately that setup uses 127.0.0.1:9000 for a socket, and none of the other sites on our droplet uses a TCP socket -- they all use this chunk for fastcgi
  
  `location ~ \.php$ {
  fastcgi_split_path_info ^(.+\.php)(/.+)$;
  fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
  fastcgi_index index.php;
  include fastcgi_params;
  }`
  
  So I tried dropping that in, no dice. Here's some of the debug info from the site's error log. I think this is where it all goes wrong:
  
  `2016/07/19 16:50:08 [debug] 4362#4362: *18 connect to unix:/var/run/php/php7.0-fpm.sock, fd:23 #20
  2016/07/19 16:50:08 [debug] 4362#4362: *18 connected
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http run request: "/index.php?"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream check client, write event:1, "/index.php"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream recv(): -1 (11: Resource temporarily unavailable)
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream request: "/index.php?"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream dummy handler
  2016/07/19 16:50:08 [debug] 4362#4362: *18 post event 00007FB15402C770
  2016/07/19 16:50:08 [debug] 4362#4362: *18 post event 00007FB15403E780
  2016/07/19 16:50:08 [debug] 4362#4362: *18 delete posted event 00007FB15402C770
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http upstream request: "/index.php?"
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http fastcgi parser: 0
  2016/07/19 16:50:08 [debug] 4362#4362: *18 http fastcgi header: "Status: 503 Service Unavailable"`
  
  (I edited it for brevity, don't think I clipped out anything relevant).
  
  For what it's worth, I tried editing PHP's www.conf settings, to allow for listening on 127.0.0.1 and port 9000, as per [this post](https://stackoverflow.com/questions/21524373/nginx-connect-failed-111-connection-refused-while-connecting-to-upstream). I knew this would break all the other sites, but I wanted to see if I could get it working -- still got a bad gateway error. (Possible that I hadn't restarted PHP after that change, though.)
  
  The bizarre thing about all this is that I have a working Craft CMS install on this same droplet. I tried duplicating its server block, which was auto-generated by Laravel Forge, but that netted me the same error message *and* didn't log anything to the error log.
  
  Anyway, that's about all I know -- I'm sure I'm leaving something out, but I'm a bit frayed by the debugging process. Would be grateful for any advice.
  
  **Tags:** php
  
  > **Comments:**
  > **username_1**: Have you tried going to `yoursite.com/admin`? That "Service Unavailable" message on the front-end could mean many things. You won't know for certain until you ping the back-end.  
  > **username_2**: When you get the 503, are you getting a square box in the center with that message or the standard nginx-styled  503 message? Craft also throws up a 503 if MySQL goes down.... might be worth a restart.  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2016-07-20. Score: 2
  
  Okay, my next stackexchange question will be "Where is the dunce cap?" because I could use one. My problem was not actually a problem, and username_1 was exactly right: I was just going to `mysite.com`, not to `mysite.com/admin`.
  
  And I see now that that was clearly stated in the install instructions, a tab that I was referring to over the course of the whole afternoon!
  
  Thanks, username_1, my morning just opened up. And to the dev of posterity who finds his way to this question and answer: I know it hurts.
  
  > **Comments:**
  > **username_3**: Thanks. Our server started returning a 503 and I needed this tip to find out the cause, thank you! ;-)  
  
  ---
  
  