Django Internal Server 500 Error AWS Elastic-Beanstalk issue


How do I fix the Django Internal Server 500 error on an AWS eb deployed application?

Do I need to change my allowed hosts in my file to have the ip address of the ec2 in elasticbeanstalk?

I enabled DEBUG and ran eb config, and eb logs. The eb deploy values are displayed below, and the eb logs values below that. How do you fix the issue that the “No module named django?”

Provided below are the output from eb logs.

link to github project. You can view all the code here


Did you do this?

If you didn’t, AWS will not know that it should install Django and other dependencies on your EC2 instances for your deployment.

Leave a Reply