Tips & notes about nginx

[Tip] Easily Deploy Flask Applications With UWSGI & Nginx


The process of deploying Flask applications with Nginx may be so hard if it's your first time. Fortunutly, you can now do it in a few steps.


Just run the following uwsgi command:

uwsgi --socket :8080 --chdir /var/www/myflaskdir --module myflaskfile:app &

Which would run your myflaskfile app on the 8080 port and will use /var/www/myflaskdir as your working directory.

Now, to make Nginx accept requests to it as a domain name, add the following to your /etc/nginx/nginx.conf file:

server {

    root /var/www/myflaskdir;

    location / {
      include         uwsgi_params;

    location ^~ static/  {
        include  /etc/nginx/mime.types;
        root /var/www/myflaskdir/;

} can be any domain name you want. Make sure the uwsgi_pass parameter is the same as the one you are using in your uwsgi command.

Finally, reload and restart your Nginx server:

sudo service nginx reload
sudo service nginx restart

[Note] Apache's .htaccess File May Not Work With Nginx


If you are transferring your websites from a web server which is running Apache to another hosting/VPS which uses Nginx, sometimes you may notice a blank white page when you try to open your new website. Nothing shows in the log files and everything seems to be working properly.

You check for MySQL, firewall, fail2ban, configuration files and everything else. But still, the problem is there: A white page showing nothing.


The problem is caused by the apache's .htaccess file. It may not be fully comptabile with what nginx can understand.

Moving the hidden .htaccess file or removing would solve the issue. Note that you may lose redirections and other stuff you had in your original .htaccess file. And which could affect your work.

[Problem] Upstream timed out (110: Connection timed out) / 504 Gateway Time-out


This problem is very common on nginx servers running WordPress sites. The reasons may vary according to your setup, but usually they are:

  • A bad WordPress plugin eating most PHP resources/requests.
  • Misconfigured PHP-FPM with nginx configuration file.
  • Low resources available on the server.


If you are running a WordPress website, try disabling all the plugins that you have on your website. If this fixes the problem, then it's just a plugin problem. Now try enabling them one by one in order to see which one is responsible for that. Once you detect it, remove it or report to the plugin's developer.

If that didn't help, make sure your server has enough resources? Check that via ps -aux, free -m and df -h. If you think you have low resources, then contact your provider to increase them. Try moving into another hosting.