切换生产设置并恢复后，Django无法找到静态文件求助

Hey there! Let's figure out why your Django static files are still MIA even after rolling back your settings. I've run into this exact issue when I was starting out, so here are the most likely fixes to check:

1. Double-check your DEBUG mode setting #

When you're prepping for deployment, you probably set DEBUG = False (smart move for production!). But here's the critical detail: Django does NOT serve static files automatically when DEBUG is off.

If you reverted STATIC_URL but left DEBUG = False, that's almost certainly part of the problem. For production, you need to set up a dedicated way to serve static files—either using a lightweight tool like WhiteNoise (super beginner-friendly) or configuring your web server (Nginx/Apache) to handle /static/ requests directly.

If you're still testing deployment locally, try temporarily setting DEBUG = True to see if the static files load then. Just remember to flip it back off for real production!

2. Make sure STATICFILES_DIRS is configured #

You mentioned only modifying STATIC_ROOT and STATIC_URL, but Django needs explicit instructions on where your original static files live (like the static folders inside your apps, or a project-level static directory).

If you have a project-wide static folder (not the staticfiles one from collectstatic), add this to your settings.py:

STATICFILES_DIRS = [
    os.path.join(BASE_DIR, 'static'),
]

This tells Django to scan that folder for static files in addition to the static folders of your installed apps. Without this line, Django might not be able to locate your CSS/JS files at all.

3. Clear browser cache and validate template references #

Sometimes the issue isn't with Django—it's your browser hanging onto old, broken paths. Try clearing your browser cache or opening the site in incognito mode to rule this out.

Also, make sure you're using Django's static template tags correctly in your HTML:

• At the top of every template that uses static files, add {% load static %}
• Reference files like <link rel="stylesheet" href="{% static 'css/main.css' %}"> instead of hardcoding /static/css/main.css

Hardcoded paths can break if your STATIC_URL ever changes, and they might not resolve correctly in deployment setups.

4. Verify collectstatic was run (if you need it) #

If you ran python manage.py collectstatic when you had STATIC_ROOT set, your static files were copied to the staticfiles directory. Even after removing STATIC_ROOT, if DEBUG = False, Django won't serve the original source files—it expects static files to be in the STATIC_ROOT location (or served by your web server).

If you want to stick with STATIC_ROOT for deployment:

1. Re-add STATIC_ROOT = os.path.join(BASE_DIR, 'staticfiles') to settings.py
2. Re-run python manage.py collectstatic to ensure all files are copied over
3. Configure your web server to point /static/ to the staticfiles folder

5. Check your web server configuration #

If you're using Nginx, Apache, or another web server to deploy your site, you need to add a rule to serve static files directly. For example, in Nginx, add this to your server block:

location /static/ {
    root /path/to/your/project/staticfiles;
}

This tells Nginx to handle all /static/ requests on its own, instead of passing them to Django's WSGI app. Without this rule, the server will return a 404 for static files even if they exist.

If you're using a PaaS like Heroku, make sure you have WhiteNoise installed and configured in settings.py and wsgi.py—it's a simple way to serve static files without a separate web server.

内容的提问来源于stack exchange，提问作者Sahand