<p>So my issue was very simple to solve once I paid better attention. The 404 was loading perfectly fine the whole time, my problem was that in my 404 file I had it as {% block content %} and not {% block main %} as I had specified in my layout.</p>

CC BY-SA 3.0
2018-05-01T17:04:18.393Z
2018-05-01T17:04:18.393Z
Darryl Hardin
<p>I found this question "<a href="https://craftcms.stackexchange.com/questions/2556/404-page-not-showing">404 Page Not Showing</a>" asked 3 years ago that the person who asked figured it out but didn't really expand on how they did.</p>

<p>I have basically the same issue, craft doesn't load the 404 error ever, it simply loads the template with nothing.
<a href="https://footwearoutfitters.net/123" rel="nofollow noreferrer">https://footwearoutfitters.net/123</a></p>

<p>I haven't edited any .htaccess files</p>

<p>Routes is left unmodified, both in the CP and the file itself.</p>

<p>I'm wondering if I setup my entries incorrectly for the URI, anyone have ideas or think of somewhere else I could give info on to help this along?</p>

<p>Here is my .htaccess folder in the public</p>

<pre><code>&lt;IfModule mod_rewrite.c&gt;
  RewriteEngine On

  # Send would-be 404 requests to Craft
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !^/(favicon\.ico|apple-touch-icon.*\.png)$ [NC]
  RewriteRule (.+) index.php?p=$1 [QSA,L]
&lt;/IfModule&gt;
</code></pre>

CC BY-SA 3.0
2018-03-27T16:32:27.557Z
Are you using Apache? If you’re using Nginx then the .htaccess files are useless.
Jalen Davenport
CC BY-SA 3.0
2018-03-27T16:44:49.690Z
That's good to know, but yes, it's Apache. I have another site hosted on this same server and it works just fine with the 404 requests
Darryl Hardin
CC BY-SA 3.0
2018-03-27T16:46:14.930Z
Cool. Do you have anything in your `404.html` template?
Jalen Davenport
CC BY-SA 3.0
2018-03-27T16:50:11.097Z
Perhaps worth your time to take a peek at this article as well -> https://nystudio107.com/blog/handling-errors-gracefully-in-craft-cms#handling-exceptions-on-the-frontend
Jalen Davenport
CC BY-SA 3.0
2018-03-28T17:30:29.460Z
I do have a 404.html, I haven't yet changed it from what craft put in. I will take a look at that article and update, thanks Jalen.
Darryl Hardin
<404-page>
404 error page not loading
# 404 error page not loading

(Asked by: username_0 on 2018-03-27)

I found this question "404 Page Not Showing" asked 3 years ago that the person who asked figured it out but didn't really expand on how they did.
I have basically the same issue, craft doesn't load the 404 error ever, it simply loads the template with nothing.
https://footwearoutfitters.net/123
I haven't edited any .htaccess files
Routes is left unmodified, both in the CP and the file itself.
I'm wondering if I setup my entries incorrectly for the URI, anyone have ideas or think of somewhere else I could give info on to help this along?
Here is my .htaccess folder in the public

  RewriteEngine On

  # Send would-be 404 requests to Craft
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
  RewriteCond %{REQUEST_URI} !^/(favicon\.ico|apple-touch-icon.*\.png)$ [NC]
  RewriteRule (.+) index.php?p=$1 [QSA,L]

**Tags:** 404-page
> **Comments:**
> **username_1**: Are you using Apache? If you’re using Nginx then the .htaccess files are useless.  
> **username_0**: That's good to know, but yes, it's Apache. I have another site hosted on this same server and it works just fine with the 404 requests  
> **username_1**: Cool. Do you have anything in your `404.html` template?  
> **username_1**: Perhaps worth your time to take a peek at this article as well -> https://nystudio107.com/blog/handling-errors-gracefully-in-craft-cms#handling-exceptions-on-the-frontend  
> **username_0**: I do have a 404.html, I haven't yet changed it from what craft put in. I will take a look at that article and update, thanks Jalen.  

---

## 1 answers

### Answer by username_0 on 2018-05-01. Score: 2 | Accepted answer

So my issue was very simple to solve once I paid better attention. The 404 was loading perfectly fine the whole time, my problem was that in my 404 file I had it as {% block content %} and not {% block main %} as I had specified in my layout.


---

