I had the same problem and adding ALLOWED_HOSTS = (“yourdomain.com”,) to settings fixed it. UPDATE: there few other possibilities: Nginx (or whatever web server you use) doesn’t pass the $host variable to the app Host contains underscores See details: https://blog.anvileight.com/posts/how-to-fix-bad-request-400-in-django/
From your comment I think this is a config problem in your django site, not a matter of gunicorn log, logs will not show more than django send to it. Here is an example of how you can configure django setting to send log to your file (instead of send it to admins by email … Read more
We had the same problem using Django+nginx+gunicorn. From Gunicorn documentation we have configured the graceful-timeout that made almost no difference. After some testings, we found the solution, the parameter to configure is: timeout (And not graceful timeout). It works like a clock.. So, Do: 1) open the gunicorn configuration file 2) set the TIMEOUT to … Read more
I just went through this problem this week and stumbled on your question along the way. Fair to say you either resolved this or changed approaches by now, but for future’s sake: The command in my Dockerfile is: CMD [“gunicorn” , “-b”, “0.0.0.0:8000”, “app:app”] Where the first “app” is the module and the second “app” … Read more
Because Gunicorn is starting with 8 workers (in your example), this forks the app 8 times into 8 processes. These 8 processes are forked from the Master process, which monitors each of their status & has the ability to add/remove workers. Each process gets a copy of your APScheduler object, which initially is an exact … Read more
You can use the chdir flag for Gunicorn to change to the project directory before executing your command. gunicorn -w 2 -b 0.0.0.0:8000 –chdir /home/telessaude/telessaude_branch_master telessaude.wsgi_dev:application –reload –timeout 900
Besides the small TCP/IP overhead, there’s not much of a difference. Each listen() socket gets a connection queue, and accept() just pops a connection from that queue. In gunicorn each worker just pops a new connection from that queue as its able so that won’t change. The difference is performance (sockets being a bit faster) … Read more
Gunicorn (and most WSGI servers) defaults to looking for the callable named application in whatever module you point it at. Adding an alias from myproject import myapp as application or application = myapp will let Gunicorn discover the callable again. However, the wsgi.py file or the alias aren’t needed, Gunicorn can be pointed directly at … Read more
It looks like the easiest way to do this is to tell gunicorn to preload your application using the preload_app option. This assumes that you can load the data structure as a module-level variable: from flask import Flask from your.application import CustomDataStructure CUSTOM_DATA_STRUCTURE = CustomDataStructure(‘/data/lives/here’) # @app.routes, etc. Alternatively, you could use a memory-mapped file … Read more
It seems that there’s a package for this called gunicorn3 (this was tested on ubuntu) sudo apt-get install gunicorn3 then running the following command should work and run gunicorn with python3: gunicorn3 –log-level debug –bind 0.0.0.0:30443 server:app