Why do I get a 110: Connection timed out error, white serving a flask app through nginx and uwsgi?nginx not able to connect to php-fpm socketuWSGI cannot find “application” using Flask and Virtualenv502 bad gateway nginx. uwsgi, flaskNginx + GUnicorn + Flask + www-data user - file lockdownConfigure basic python 3.5, flask, uwsgi, nginx appNginx and uWSGI Flask app Connection RefusedNginx: use uwsgi_pass with a proxy_pass fallback?Nginx cannot see unix socketFastCGI: Access deniednginx (13: Permission denied) on socket

Why do real positive eigenvalues result in an unstable system? What about eigenvalues between 0 and 1? or 1?

Is it acceptable to use working hours to read general interest books?

"The cow" OR "a cow" OR "cows" in this context

Co-worker works way more than he should

Mistake in years of experience in resume?

What was Apollo 13's "Little Jolt" after MECO?

Why must Chinese maps be obfuscated?

How do I reattach a shelf to the wall when it ripped out of the wall?

Is Electric Central Heating worth it if using Solar Panels?

Find the identical rows in a matrix

What does a straight horizontal line above a few notes, after a changed tempo mean?

Creating a chemical industry from a medieval tech level without petroleum

What is the most expensive material in the world that could be used to create Pun-Pun's lute?

Is there any pythonic way to find average of specific tuple elements in array?

Combinatorics problem, right solution?

"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?

Magical attacks and overcoming damage resistance

Why do distances seem to matter in the Foundation world?

How much of a wave function must reside inside event horizon for it to be consumed by the black hole?

How to not starve gigantic beasts

As an international instructor, should I openly talk about my accent?

Can a stored procedure reference the database in which it is stored?

Which big number is bigger?

Should the Product Owner dictate what info the UI needs to display?



Why do I get a 110: Connection timed out error, white serving a flask app through nginx and uwsgi?


nginx not able to connect to php-fpm socketuWSGI cannot find “application” using Flask and Virtualenv502 bad gateway nginx. uwsgi, flaskNginx + GUnicorn + Flask + www-data user - file lockdownConfigure basic python 3.5, flask, uwsgi, nginx appNginx and uWSGI Flask app Connection RefusedNginx: use uwsgi_pass with a proxy_pass fallback?Nginx cannot see unix socketFastCGI: Access deniednginx (13: Permission denied) on socket






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















I am trying to serve a flask application using nginx and uwsgi, through an ubuntu docker container, while the host is also an ubuntu 18.04 OS.



This is the conf file for the nginx server, for which I have created a symbolic link in /etc/nginx/sites-enabled:



server 
listen 1611;
real_ip_header X-Forwarded-For;
set_real_ip_from 127.0.0.1;
server_name localhost;

location /
include uwsgi_params;
uwsgi_pass unix:/var/www/html/step_service/socket.sock;
uwsgi_modifier1 30;




The `uwsgi.ini' file is as follows:



[uwsgi]
base=/var/www/html/step_service
app=app
module=%(app)
callable = app

home=%(base)/venv
pythonpath=%(base)
socket=%(base)/socket.sock
chmod-socket=777

master=true
processes=5
threads=5
die-on-term=true
autostart=true
autorestart=true
harakiri=30
logto=/var/www/html/step_service/log/%n.log


The logs of uwsgi seem to indicate success:



 * Serving Flask app "app" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
* Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)


The logs of nginx server (in particular error.log) is:



2019/04/18 16:23:30 [error] 6729#6729: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "GET /rec/1/1 HTTP/1.1
", upstream: "uwsgi://unix:/var/www/html/step_service/socket.sock", host: "172.17.0.2:1611"


Any ideas would be more than welcome!










share|improve this question

















  • 1





    Did you use the right uwsgi.ini? Your app is listening on TCP port 5000, not on the Unix socket specified. You should also heed the warning about using a production uwsgi server. And the nginx server on port 1611 is utterly redundant. Just have your uwsgi server listen on that port if you want it there.

    – Michael Hampton
    Apr 18 at 16:59












  • The warning comes from Flask, and that's why I'm using wsgi with nginx. But how should I specify a socket that listens to port 5000?

    – Dimitris Poulopoulos
    Apr 18 at 17:27











  • uwsgi-docs.readthedocs.io/en/latest/Configuration.html It's the very first example...

    – Michael Hampton
    Apr 18 at 17:30

















0















I am trying to serve a flask application using nginx and uwsgi, through an ubuntu docker container, while the host is also an ubuntu 18.04 OS.



This is the conf file for the nginx server, for which I have created a symbolic link in /etc/nginx/sites-enabled:



server 
listen 1611;
real_ip_header X-Forwarded-For;
set_real_ip_from 127.0.0.1;
server_name localhost;

location /
include uwsgi_params;
uwsgi_pass unix:/var/www/html/step_service/socket.sock;
uwsgi_modifier1 30;




The `uwsgi.ini' file is as follows:



[uwsgi]
base=/var/www/html/step_service
app=app
module=%(app)
callable = app

home=%(base)/venv
pythonpath=%(base)
socket=%(base)/socket.sock
chmod-socket=777

master=true
processes=5
threads=5
die-on-term=true
autostart=true
autorestart=true
harakiri=30
logto=/var/www/html/step_service/log/%n.log


The logs of uwsgi seem to indicate success:



 * Serving Flask app "app" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
* Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)


The logs of nginx server (in particular error.log) is:



2019/04/18 16:23:30 [error] 6729#6729: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "GET /rec/1/1 HTTP/1.1
", upstream: "uwsgi://unix:/var/www/html/step_service/socket.sock", host: "172.17.0.2:1611"


Any ideas would be more than welcome!










share|improve this question

















  • 1





    Did you use the right uwsgi.ini? Your app is listening on TCP port 5000, not on the Unix socket specified. You should also heed the warning about using a production uwsgi server. And the nginx server on port 1611 is utterly redundant. Just have your uwsgi server listen on that port if you want it there.

    – Michael Hampton
    Apr 18 at 16:59












  • The warning comes from Flask, and that's why I'm using wsgi with nginx. But how should I specify a socket that listens to port 5000?

    – Dimitris Poulopoulos
    Apr 18 at 17:27











  • uwsgi-docs.readthedocs.io/en/latest/Configuration.html It's the very first example...

    – Michael Hampton
    Apr 18 at 17:30













0












0








0








I am trying to serve a flask application using nginx and uwsgi, through an ubuntu docker container, while the host is also an ubuntu 18.04 OS.



This is the conf file for the nginx server, for which I have created a symbolic link in /etc/nginx/sites-enabled:



server 
listen 1611;
real_ip_header X-Forwarded-For;
set_real_ip_from 127.0.0.1;
server_name localhost;

location /
include uwsgi_params;
uwsgi_pass unix:/var/www/html/step_service/socket.sock;
uwsgi_modifier1 30;




The `uwsgi.ini' file is as follows:



[uwsgi]
base=/var/www/html/step_service
app=app
module=%(app)
callable = app

home=%(base)/venv
pythonpath=%(base)
socket=%(base)/socket.sock
chmod-socket=777

master=true
processes=5
threads=5
die-on-term=true
autostart=true
autorestart=true
harakiri=30
logto=/var/www/html/step_service/log/%n.log


The logs of uwsgi seem to indicate success:



 * Serving Flask app "app" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
* Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)


The logs of nginx server (in particular error.log) is:



2019/04/18 16:23:30 [error] 6729#6729: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "GET /rec/1/1 HTTP/1.1
", upstream: "uwsgi://unix:/var/www/html/step_service/socket.sock", host: "172.17.0.2:1611"


Any ideas would be more than welcome!










share|improve this question














I am trying to serve a flask application using nginx and uwsgi, through an ubuntu docker container, while the host is also an ubuntu 18.04 OS.



This is the conf file for the nginx server, for which I have created a symbolic link in /etc/nginx/sites-enabled:



server 
listen 1611;
real_ip_header X-Forwarded-For;
set_real_ip_from 127.0.0.1;
server_name localhost;

location /
include uwsgi_params;
uwsgi_pass unix:/var/www/html/step_service/socket.sock;
uwsgi_modifier1 30;




The `uwsgi.ini' file is as follows:



[uwsgi]
base=/var/www/html/step_service
app=app
module=%(app)
callable = app

home=%(base)/venv
pythonpath=%(base)
socket=%(base)/socket.sock
chmod-socket=777

master=true
processes=5
threads=5
die-on-term=true
autostart=true
autorestart=true
harakiri=30
logto=/var/www/html/step_service/log/%n.log


The logs of uwsgi seem to indicate success:



 * Serving Flask app "app" (lazy loading)
* Environment: production
WARNING: Do not use the development server in a production environment.
Use a production WSGI server instead.
* Debug mode: off
* Running on http://0.0.0.0:5000/ (Press CTRL+C to quit)


The logs of nginx server (in particular error.log) is:



2019/04/18 16:23:30 [error] 6729#6729: *1 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 172.17.0.1, server: localhost, request: "GET /rec/1/1 HTTP/1.1
", upstream: "uwsgi://unix:/var/www/html/step_service/socket.sock", host: "172.17.0.2:1611"


Any ideas would be more than welcome!







nginx docker uwsgi flask






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Apr 18 at 16:31









Dimitris PoulopoulosDimitris Poulopoulos

1




1







  • 1





    Did you use the right uwsgi.ini? Your app is listening on TCP port 5000, not on the Unix socket specified. You should also heed the warning about using a production uwsgi server. And the nginx server on port 1611 is utterly redundant. Just have your uwsgi server listen on that port if you want it there.

    – Michael Hampton
    Apr 18 at 16:59












  • The warning comes from Flask, and that's why I'm using wsgi with nginx. But how should I specify a socket that listens to port 5000?

    – Dimitris Poulopoulos
    Apr 18 at 17:27











  • uwsgi-docs.readthedocs.io/en/latest/Configuration.html It's the very first example...

    – Michael Hampton
    Apr 18 at 17:30












  • 1





    Did you use the right uwsgi.ini? Your app is listening on TCP port 5000, not on the Unix socket specified. You should also heed the warning about using a production uwsgi server. And the nginx server on port 1611 is utterly redundant. Just have your uwsgi server listen on that port if you want it there.

    – Michael Hampton
    Apr 18 at 16:59












  • The warning comes from Flask, and that's why I'm using wsgi with nginx. But how should I specify a socket that listens to port 5000?

    – Dimitris Poulopoulos
    Apr 18 at 17:27











  • uwsgi-docs.readthedocs.io/en/latest/Configuration.html It's the very first example...

    – Michael Hampton
    Apr 18 at 17:30







1




1





Did you use the right uwsgi.ini? Your app is listening on TCP port 5000, not on the Unix socket specified. You should also heed the warning about using a production uwsgi server. And the nginx server on port 1611 is utterly redundant. Just have your uwsgi server listen on that port if you want it there.

– Michael Hampton
Apr 18 at 16:59






Did you use the right uwsgi.ini? Your app is listening on TCP port 5000, not on the Unix socket specified. You should also heed the warning about using a production uwsgi server. And the nginx server on port 1611 is utterly redundant. Just have your uwsgi server listen on that port if you want it there.

– Michael Hampton
Apr 18 at 16:59














The warning comes from Flask, and that's why I'm using wsgi with nginx. But how should I specify a socket that listens to port 5000?

– Dimitris Poulopoulos
Apr 18 at 17:27





The warning comes from Flask, and that's why I'm using wsgi with nginx. But how should I specify a socket that listens to port 5000?

– Dimitris Poulopoulos
Apr 18 at 17:27













uwsgi-docs.readthedocs.io/en/latest/Configuration.html It's the very first example...

– Michael Hampton
Apr 18 at 17:30





uwsgi-docs.readthedocs.io/en/latest/Configuration.html It's the very first example...

– Michael Hampton
Apr 18 at 17:30










0






active

oldest

votes












Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963697%2fwhy-do-i-get-a-110-connection-timed-out-error-white-serving-a-flask-app-throug%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Server Fault!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f963697%2fwhy-do-i-get-a-110-connection-timed-out-error-white-serving-a-flask-app-throug%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

RemoteApp sporadic failureWindows 2008 RemoteAPP client disconnects within a matter of minutesWhat is the minimum version of RDP supported by Server 2012 RDS?How to configure a Remoteapp server to increase stabilityMicrosoft RemoteApp Active SessionRDWeb TS connection broken for some users post RemoteApp certificate changeRemote Desktop Licensing, RemoteAPPRDS 2012 R2 some users are not able to logon after changed date and time on Connection BrokersWhat happens during Remote Desktop logon, and is there any logging?After installing RDS on WinServer 2016 I still can only connect with two users?RD Connection via RDGW to Session host is not connecting

How to write a 12-bar blues melodyI-IV-V blues progressionHow to play the bridges in a standard blues progressionHow does Gdim7 fit in C# minor?question on a certain chord progressionMusicology of Melody12 bar blues, spread rhythm: alternative to 6th chord to avoid finger stretchChord progressions/ Root key/ MelodiesHow to put chords (POP-EDM) under a given lead vocal melody (starting from a good knowledge in music theory)Are there “rules” for improvising with the minor pentatonic scale over 12-bar shuffle?Confusion about blues scale and chords

Esgonzo ibérico Índice Descrición Distribución Hábitat Ameazas Notas Véxase tamén "Acerca dos nomes dos anfibios e réptiles galegos""Chalcides bedriagai"Chalcides bedriagai en Carrascal, L. M. Salvador, A. (Eds). Enciclopedia virtual de los vertebrados españoles. Museo Nacional de Ciencias Naturales, Madrid. España.Fotos