did you find anhy answer ?
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,127854,271666#msg-271666
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Sun, Aug 14, 2016 at 08:03:21PM -0400, Larry Martell wrote:
> On Tue, Aug 9, 2016 at 10:35 PM, Richard Stanway
> wrote:
Hi there,
> I have some requests that can take a long time to return - the users
> can request huge amount of data to be pulled from very large database
> tables with comple
right? But I get the 504 response before 10 minutes
have passed since the request is sent. Why is that?
>
> On Tue, Aug 9, 2016 at 11:09 PM, Larry Martell
> wrote:
>>
>> I just set up a django site with nginx and uWSGI. Some pages I go to
>> work fine, but other fail with a
il with a 504 Gateway Time-out. I used to
> serve this site with apache and wsgi and these same pages worked fine.
>
> This is what I see in the nginx error log:
>
> 2016/08/09 16:40:19 [error] 17345#0: *1 upstream timed out (110:
> Connection timed out) while reading response hea
I just set up a django site with nginx and uWSGI. Some pages I go to
work fine, but other fail with a 504 Gateway Time-out. I used to
serve this site with apache and wsgi and these same pages worked fine.
This is what I see in the nginx error log:
2016/08/09 16:40:19 [error] 17345#0: *1
On Thu, Jun 4, 2015 at 10:27 PM, Thiago Farina wrote:
> Hi!
>
> Could nginx be the cause of (google chrome message):
>
> "
> This webpage is not available
>
> ERR_CONNECTION_TIMED_OUT
> "
>
> My IP change is dynamic and changed this afternoon, and after that all
> I'm getting now is this TIMEOUT.
Hi!
Could nginx be the cause of (google chrome message):
"
This webpage is not available
ERR_CONNECTION_TIMED_OUT
"
My IP change is dynamic and changed this afternoon, and after that all
I'm getting now is this TIMEOUT. I have stopped and restarted nginx
many times now but still the same proble
Hi i create a module which is parse a post request.
But it able to parse first post but other are getting time out what's the
problem?
Registering parser by ngx_http_read_client_request_body(r,
ngx_http_ab_router_post_read);
and try to parse request by
b = r->request_body-&g
Maxim,
Thank you for your reply.
On Thu, Jan 9, 2014 at 10:03 AM, Maxim Dounin wrote:
> [snip]
>
> If you are able to connect to localhost:9090 with your browser,
> you are likely using native HTTP support in your uWSGI server.
>
Yes, I am starting the uwsgi process like this, using the --http
ost:9090, everything works as expected.
>
> When I change the nginx config file to use uwsgi_pass to localhost:9090 as
> described here --
> http://uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html#putting-behind-a-full-webserver--
> however, I get time out errors:
>
> >
uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html#putting-behind-a-full-webserver--
however, I get time out errors:
> upstream timed out (110: Connection timed out) while reading response
header from upstream
It is as though nginx is *not* passing those requests to the uwsgi process
(
On 8/26/2013 11:25 AM, Lukas Tribus wrote:
> Hi!
>
>
>> If this were the root cause, wouldn't the cURL call fail in the way way,
>> regardless of the CURLOPT_SSL_VERIFYPEER value? In other words, it
>> doesn't seem like changing this cURL option would change the number of
>> backend processes r
Hi!
> If this were the root cause, wouldn't the cURL call fail in the way way,
> regardless of the CURLOPT_SSL_VERIFYPEER value? In other words, it
> doesn't seem like changing this cURL option would change the number of
> backend processes required to handle the request(s). But I could be wrong.
Thanks for the suggestion, itpp2012.
I tried adding those directives to the batch script that starts
php-cgi.exe, but the problem persists.
What I find strange is that the problem occurs only when I set peer
verification to false:
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
When I set this
set PHP_FCGI_CHILDREN=0
set PHP_FCGI_MAX_REQUESTS=1
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,242154,242181#msg-242181
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
function to a
secure URL (https protocol), and I disable peer verification, like this
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
nginx responds with a "504 Gateway Time-out".
If I set CURLOPT_SSL_VERIFYPEER to TRUE, nginx responds with a "200 OK",
although curl_exec()
function to a
>>>> secure URL (https protocol), and I disable peer verification, like this
>>>>
>>>> curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
>>>>
>>>> nginx responds with a "504 Gateway Time-out".
>>>>
>>>&g
;m seeing a strange problem with nginx (1.5.2 on Windows) and PHP
> >> (5.4.8 on Windows).
> >>
> >> Whenever I make a cURL request with PHP's curl_exec() function to a
> >> secure URL (https protocol), and I disable peer verification, like this
> &
I make a cURL request with PHP's curl_exec() function to a
>> secure URL (https protocol), and I disable peer verification, like this
>>
>> curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
>>
>> nginx responds with a "504 Gateway Time-out".
>>
>
s protocol), and I disable peer verification, like this
>
> curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, FALSE);
>
> nginx responds with a "504 Gateway Time-out".
>
> If I set CURLOPT_SSL_VERIFYPEER to TRUE, nginx responds with a "200 OK",
> although curl_exec()
E);
nginx responds with a "504 Gateway Time-out".
If I set CURLOPT_SSL_VERIFYPEER to TRUE, nginx responds with a "200 OK",
although curl_exec() returns false, which is expected due to the
verification failure (I'm using a self-signed certificate in nginx).
I have tried executi
Hi, I am also a Media Temple customer and its knowledgebase has not been
updated with this issue although it is very frequent from what I see.
Thank you very much.
I changed the nginx.conf file adding the lines you mentioned and then
restarted.
It also helped me a lot finding the nginx restart c
22 matches
Mail list logo
