Django部署Elastic Beanstalk时WSGIPath路径不存在报错求助

Let’s work through this issue together—this is one of the most common snags when deploying Django to Elastic Beanstalk, so you’re definitely not alone here.

Step 1: Double-Check Your Project Structure #

First, let’s make sure you’re targeting the right file. The WSGIPath needs to point to your Django project’s wsgi.py file, using the format [your-django-project-name].wsgi:application.

Take a look at your project root (the folder that contains manage.py). You should see a subfolder with your Django project name (the one created when you ran django-admin startproject). Inside that folder, there must be a wsgi.py file.

For example, if your structure looks like this:

project-root/
├── .ebextensions/
│   └── django.config
├── shofidecksite/
│   ├── __init__.py
│   ├── settings.py
│   ├── urls.py
│   └── wsgi.py
├── manage.py
└── requirements.txt

Then shofidecksite.wsgi:application is the correct path—but only if that subfolder and file actually exist. If your project folder has a different name (like shofi instead of shofidecksite), that’s where you need to adjust the path.

Step 2: Fix YAML Indentation in Your django.config #

YAML files are extremely picky about indentation, and a single missing space can break your entire configuration. Your django.config should look exactly like this (notice the 2-space indentation for each nested level):

option_settings:
  aws:elasticbeanstalk:container:python:
    WSGIPath: shofidecksite.wsgi:application

If your indentation is off (e.g., tabs instead of spaces, or inconsistent spacing), Elastic Beanstalk might not read the setting correctly, leading to the "file not found" error.

Step 3: Try a Direct File Path Instead #

If you’re still unsure about the module path, you can specify the relative file path to wsgi.py directly. This is often more straightforward:

option_settings:
  aws:elasticbeanstalk:container:python:
    WSGIPath: shofidecksite/wsgi.py

Elastic Beanstalk will automatically look for the application object inside this file, so this should work as long as the file exists at that path.

Step 4: Verify the Path in Your EB Environment #

To confirm what’s actually on your Elastic Beanstalk instance, connect to it using SSH:

1. Run eb ssh from your project root (make sure you have the EB CLI installed).
2. Once connected, navigate to the application directory with cd /var/app/current/.
3. List the contents with ls -la to check if your Django project folder exists, then go into it with cd shofidecksite and run ls to confirm wsgi.py is there.

If the file doesn’t exist here, that means your deployment isn’t copying the correct files—double-check that you’re committing all necessary project files to your git repo before running eb deploy.

Final Checks #

• Make sure you’re not confusing your Elastic Beanstalk application/environment name with your Django project name—they don’t have to match, and the WSGIPath only cares about the Django project folder name.
• After updating your django.config, run eb deploy to push the changes to your environment. You can also verify the active WSGIPath setting with eb config—look for the aws:elasticbeanstalk:container:python section.

Most of the time, this error comes down to a misspelled project name, bad YAML indentation, or missing files in your deployment. Once you fix those, your app should start up correctly!

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