Answers.Body: <p>It turns out it was because I had Apache running and on port 80. I saw something about this somewhere in the guides I followed, but forgot to come back and stop Apache. Oops.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-07T20:00:58.723Z
Answers.Text: Hey  I wrote the article you linked in your question. Glad you solved the issue!
Answers.UserDisplayName: Jalen Davenport
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-07T21:12:30.677Z
Answers.Text: @JalenDavenport Woo, big thanks for that article! Helped a lot, since the other ways were dead ends.
Answers.UserDisplayName: BBaysinger
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-07T19:00:42.177Z
Answers.LastActivityDate: 2019-03-07T19:00:42.177Z
Answers.UserDisplayName: BBaysinger
Body: <p>Trying to get started with Craft CMS 3 for the first time, and it's running locally via Valet. from the front end, I get:</p>
  
  <blockquote>
  <pre><code>&gt; HTTP 503 – Service Unavailable – craft\web\ServiceUnavailableHttpException
  </code></pre>
  </blockquote>
  
  <p>And on the admin side, I'm getting a 404. I've looked at similar questions, but none of the answers are helping me. I've set this up twice following <a href="https://medium.com/@jalendport/running-craft-cms-3-on-laravel-valet-6df61e5193fd" rel="nofollow noreferrer">this article on running Craft with Valet</a>, and gotten the same result both times.</p>
  
Tags: <craft3><valet>
Title: ServiceUnavailableHttpException on front end, and 404 on admin
ThreadText: # ServiceUnavailableHttpException on front end, and 404 on admin
  
  (Asked by: username_0 on 2019-03-07)
  
  Trying to get started with Craft CMS 3 for the first time, and it's running locally via Valet. from the front end, I get:
  
  > ```
  > > HTTP 503 – Service Unavailable – craft\web\ServiceUnavailableHttpException
  >
  > ```
  
  And on the admin side, I'm getting a 404. I've looked at similar questions, but none of the answers are helping me. I've set this up twice following [this article on running Craft with Valet](https://medium.com/@jalendport/running-craft-cms-3-on-laravel-valet-6df61e5193fd), and gotten the same result both times.
  
  **Tags:** craft3, valet
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2019-03-07. Score: 2 | Accepted answer
  
  It turns out it was because I had Apache running and on port 80. I saw something about this somewhere in the guides I followed, but forgot to come back and stop Apache. Oops.
  
  > **Comments:**
  > **username_1**: Hey  I wrote the article you linked in your question. Glad you solved the issue!  
  > **username_0**: @username_1 Woo, big thanks for that article! Helped a lot, since the other ways were dead ends.  
  
  ---
  
  