Django; AWS Elastic Beanstalk ERROR: Your WSGIPath refers to a file that does not exist

Question

I am using this tutorial: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/create-deploy-python-django.html

I create the .ebextensions directory inside the root directory, and put this django.config file in it:

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

I've also tried setting the path to mysite/mysite/wsgi.py because I saw that work somewhere but it did not help me.

Everywhere I look shows a different .config file with different arrangements, and I don't know where to go from here. How can I properly set my WSGIPath in Elastic Beanstalk?

Do you have this file .elasticbeanstalk/optionsettings? – Piyush Patil Jul 29 '16 at 10:17 — Piyush Patil, Jul 29 '16 at 10:17

score 25 · Accepted Answer · answered Sep 05 '17 at 14:13

25

[Solution]

1 eb config

2 Change the WSGIPath there from application.py to mysite/wsgi.py

That's It

answered Sep 05 '17 at 14:13

karan

398
4
5

1

Does the django.config not do anything then? – Aviendha Apr 03 '18 at 14:49
3

Three years later and this is still helping people. The really needs clearing up in the AWS tutorial! – goose Jun 30 '19 at 11:28
1

Does the eb config in the answer refer to the django.config file? – Chris Claude Dec 02 '19 at 14:31
this comment was very helpful! -- one note, it is specific to using python 3.6 (which is now deprecated, and unfortunately still used in the tutorial linked). this issue shouldn't happen when using python 3.8 and Linux 2 ([platform history](https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platform-history-python.html)) – willwrighteng Sep 25 '21 at 19:12

score 2 · Answer 2 · answered Apr 03 '18 at 15:15

I ran into a similar issue, and it seemed to resolve when I put .elasticbeanstalk in the same directory as .ebextensions, rather than having it be a child directory. Then I had to run eb config to fix the wsgi file that it was de facto picking up, and now I have a running app.

score 2 · Answer 3 · answered Feb 07 '19 at 18:26

Make sure that .ebextensions isn't ignored. EB looks for .ignore file (.ebignore by default and if it doesnt exists but .gitignore does, it will use it) and deploy only the files that are not ignored. Had a similar issue with my local_settings.

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html#eb-cli3-ebignore

Display name · Answer 4 · 2020-09-13T19:37:02.573

If you see the following error:

ERROR: Your WSGIPath refers to a file that does not exist.

Note the following:

EC2 (server) instances in EB (platform) run Apache.
Apache finds Python apps according to our WSGIPATH.
By default EB assumes the WSGI file is called application.py.

There are two ways of correcting this.

Option 1: Using environment-specific configuration settings

Run: $ eb config

Find the following config file “.elasticbeanstalk/src-test.env.yml.” This file doesn’t actually exist locally; EB pulled it so that you can edit it. If you save changes in this pseudo-file, EB will update the corresponding settings in your env.

If you search for the terms ‘WSGI’ in the file, you should find a config section resembling this:

aws:elasticbeanstalk:container:python:
  NumProcesses: '1'
  NumThreads: '15'
  StaticFiles: /static/=static/
  WSGIPath: application.py

Update the WSGIPath:

 aws:elasticbeanstalk:container:python:
   NumProcesses: '1'
   NumThreads: '15'
   StaticFiles: /static/=static/
   WSGIPath: src/src/wsgi.py #src/src is an example. Do not just c&p.

If you save the file, EB will update the env config automatically.

The advantage to using the $ eb config method to change settings is that you can specify different settings per env.

Option 2: Using global configuration settings

To use this option, create a new file called /.ebextensions/02_python.config:

option_settings:
  "aws:elasticbeanstalk:application:environment":
    DJANGO_SETTINGS_MODULE: “src.settings" #src is an example.
    "PYTHONPATH": "/opt/python/current/app/src:$PYTHONPATH" #src is an example.
  "aws:elasticbeanstalk:container:python":
    WSGIPath: src/src/wsgi.py #src is an example.
    NumProcesses: 3
    NumThreads: 20
  "aws:elasticbeanstalk:container:python:staticfiles":
    "/static/": "www/static/"

What’s happening?

DJANGO_SETTINGS_MODULE: "src.settings" - adds the path to the settings module.
"PYTHONPATH": "/opt/python/current/app/src:$PYTHONPATH" - updates our PYTHONPATH so Python can find the modules in our application.(Note that the use of the full path is necessary.)
WSGIPath: src/src/wsgi.py sets our WSGI Path.
NumProcesses: 3 and NumThreads: 20 - updates the number of processes and threads used to run our WSGI application.
"/static/": "www/static/" sets our static files path.

Run $ git commit (if necessary) and $ eb deploy to update these settings.

score 1 · Answer 5 · answered May 29 '20 at 19:55

I did not use console but GUI.

ERROR: Your WSGIPath refers to a file that does not exist.

where could be problem : Creating .zip file

select all : files of your project (not the project folder)

Note : weworkout is my django project (created by django-admin startproject weworkout)

Right way : select all files

Wrong way : selecting project folder

Also this is the only change you have to do to your django project before uploading

weworkout/.ebextensions/django.config file contains

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

Note : .ebextensions is in same folder as manage.py

score 0 · Answer 6 · answered Jul 30 '20 at 21:16

0

Check if your Django.config file was saved with the correct extension. I had the same issue and the problem was that the file was being saved as a TXT file instead of config file.

answered Jul 30 '20 at 21:16

Ale Silva

73
1
1
5

Django; AWS Elastic Beanstalk ERROR: Your WSGIPath refers to a file that does not exist

6 Answers6