- Newest
- Most votes
- Most comments
These errors typically indicate a server problem with your application. In the context of Elastic Beanstalk, it is possible that your Django application was not properly deployed or that it is experiencing a post-deployment error. To troubleshoot We need to download logs and check them Look in var-XX/logs/log/eb-activity.log for deployment errors If the error is coming from your Django application itself, look in var-XX/app/support/logs/passenger.log and production.log.
This would be my structure, but the wsgi.py module can not be found
My nginx/error.log says "Connection refused while connecting to upstream.
My eb-engine.log seems fine except two warnings that say that processes httpd and xray are not registered
I should add too that I am currently using the eb console, not CLI. I am uploading a zipped ebdjango folder. The outmost one
These are the contents of the zipped folder I am uploading
Relevant content
- asked 5 months ago
- asked 10 months ago
- asked 5 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Hello, sorry for responding so late. I managed to solve problem 1, however problem 2 still persists.
My logs say that my application module can not be found. I am using the same folder structure as in the tutorial. My web.stdout.log is the one that says "No module named ****".