Why do I see apache's 404 and not Django custom 404?

Question

On my local django runserver I created a custom templates/404.html, and this works no problem. However in production with apache this custom 404.html is no longer shown (even with DEBUG=False).

I just get a white page with

Not Found

The requested URL /blahblah was not found on this server.

I don't believe that this isn't even the django default, but rather something to do with apache.

How do I tell apache to let django handle the 404s?

Have you compared the Apache configuration files in your dev and production servers? — Tero Kilkanen, Aug 12 '14 at 22:06
The dev server that I mention is the django runserver not apache. Updated my OP. — fpghost, Aug 12 '14 at 22:33
You need to set up Apache so that error pages are served by Django. You should be able to find guides to do this. — Tero Kilkanen, Aug 12 '14 at 23:03

score 1 · Answer 1 · answered Aug 13 '14 at 15:02

After all that I simply had forgotten to set the needed permissions for the template on the production server(I'm running mod_wsgi in daemon mode as 'djangoUser'), so I needed

dr-x------  djangoUser djangoUser  templates
dr-------   djangoUser djangoUser  templates/404.html

d'oh.

score 0 · Answer 2 · edited May 23 '17 at 12:41

0

You have to enable the error404 handler in your Django app (see https://stackoverflow.com/questions/17662928/django-creating-a-custom-500-404-error-page) for more information on how to do this.

edited May 23 '17 at 12:41

Community

1

answered Aug 13 '14 at 04:56

deagh

1,969
5
18
16

1

I don't think that is the issue, the default 404 handler fits my needs, and django knows where to find my custom "404.html" template in my project (as shown in the local runserver). – fpghost Aug 13 '14 at 14:50

Why do I see apache's 404 and not Django custom 404?

2 Answers2