On Thu, Jun 24, 2021 at 03:36:42PM -0400, TheMask wrote:
Hi there,
> From last 8-9months we are facing one issue in which nginx 500 response
> spike obseved. And we didnt see any call to upstream. It seems like Nginx
> caches the 500 response and that us served back to user.
> We have to restart
Does anyone know what are all the status code Nginx caches by default and
why its caching 500 response.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,291914,291920#msg-291920
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/m
Hi everyone,
We are using Nginx as reverse proxy.
>From last 8-9months we are facing one issue in which nginx 500 response
spike obseved. And we didnt see any call to upstream. It seems like Nginx
caches the 500 response and that us served back to user.
We have to restart the Nginx every time when
s. &, The site's accessible hosted on
Nginx; I can get to the app's login page -- securely.
But when I enter login credentials & submit, I get an nginx/fastcgi
http fastcgi header: "Status: 500 Internal Server Error"
and in Nextcloud logs,
"Someth
Hi,
Just want to inform that we're still facing this issue with mp4.
Regards.
Shahzaib
On Mon, Mar 23, 2015 at 7:10 PM, shahzaib shahzaib
wrote:
> Hi,
>
>Nginx logging mp4 related error intermittently. Following is the log :
>
> 2015/03/23 19:01:53 [crit] 8671#0: *782950 pread()
> "/t
Hi,
Nginx logging mp4 related error intermittently. Following is the log :
2015/03/23 19:01:53 [crit] 8671#0: *782950 pread()
"/tunefiles/storage17/files/videos/2014/05/07/13994800482e2b0-360.mp4"
failed (22: Invalid argument), client: 182.178.204.162, server:
storage17.domain.com, request: "
Thanks for the tips and the corrections , after a long night i have finished
the proxy configuration with ldap auth php authentication .
Does anybody know if it it possible share configurations into ngnix page ?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257206,257245#msg-257245
I changed the IP address into my php script and i think we are moving on,
now i'm seening the next error into my logs:
*6 upstream sent invalid response: "550 5.7.0 Error: insufficient
authorization" while reading response from upstream, client: 192.168.122.1
using starttls, server: 0.0.0.0:587,
Sorry, me mistake, all the IP's are related to with the
192.168.122.0/255.255.255.0 network.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,257206,257233#msg-257233
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listi
On Thu, Mar 12, 2015 at 07:25:09PM -0400, dominus.ceo wrote:
> upstream timed out (110: Connection timed out) while connecting to
> upstream, client: 192.168.122.1, server: 0.0.0.0:143, login:
> "ricardo.carrillo", upstream: 192.168.192.78:143
Your client connected to nginx port 143 (for imap).
Hi there,
I have decided delete all authetication part from the email process auth,
and first made the simplest configuration, so i have configured nginx based
on the the examples provided into wiki nginx page and just modified it to
get an IP address and hostname to redirect my users to my back
Thank's in advance.
The php ngnix integration already worked fine, but your idea it is goot to
know what else is obtained with the manual request, I put the result of the
execution:
168.122.170:80/correo-proxy-auth/auth.php
* About to connect() to 192.168.122.170 port 80 (#0)
* Trying 192.168.
quot; \
> > -H "Auth-Protocol: imap" \
> > -H "Auth-Login-Attempt: 1" \
> > -i http://192.168.122.170:80/correo-proxy-auth/index.php
> HTTP/1.1 500 Internal Server Error
> Server: nginx/1.6.2
> Date: Wed, 11 Mar 2015 23:18:54 GMT
> Content-Type: te
-i http://192.168.122.170:80/correo-proxy-auth/index.php
HTTP/1.1 500 Internal Server Error
Server: nginx/1.6.2
Date: Wed, 11 Mar 2015 23:18:54 GMT
Content-Type: text/html
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/5.4.16
but the error logs are not very descriptive.
Posted
On Wed, Mar 11, 2015 at 03:16:51PM -0400, dominus.ceo wrote:
Hi there,
It sounds like one problem you have is the auth_http request not getting
the expected response.
See the example at
http://nginx.org/en/docs/mail/ngx_mail_auth_http_module.html#protocol, and
try making the request manually and
(i get this from the
ldap.ife.org.mx)
$getMailServ = $e->getMailServer($user);
#print "$getMailHost $getProtocol $getMailServ $user
$password
d) I pass the data above got it to generate ngnix headers
$e->setStatusPass($getMailSer
Well, thats actually good idea... And after some tweaking with my tomcat,
that was an issue! I don't know how, but tomcat stopped working and didn't
restart properly!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252546,252556#msg-252556
___
You aren't really helping, as I said, site was working FOR YEARS!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252546,252549#msg-252549
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Wed, Aug 13, 2014 at 03:59:21PM -0400, Googlemo wrote:
Hi there,
> connect() failed (110: Connection timed out) while connecting to upstream
> writev() failed (110: Connection timed out) while sending request to
> upstream
> recv() failed (104: Connection reset by peer) while connecting to ups
1.0.11 ?? that went out with the dinosaurs.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252546,252548#msg-252548
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Site was working fine for years... And suddenly I get this error. tried
reboot server - nothing, looking into logs and I see this kinds of errors:
connect() failed (110: Connection timed out) while connecting to upstream
writev() failed (110: Connection timed out) while sending request to
upstream
Yeah, Steve! You're right. Thanks. nginx config dir had rwx for root:wheel
only. Need to sleep :-).
--- Original message ---
From: "Steve Holdoway"
Date: 25 June 2013, 00:25:26
> On Tue, 2013-06-25 at 00:20 +0300, wishmaster wrote:
> >
> > --- Original message ---
> > From: "Reinis Rozit
On Tue, 2013-06-25 at 00:20 +0300, wishmaster wrote:
>
> --- Original message ---
> From: "Reinis Rozitis"
> Date: 24 June 2013, 23:00:48
>
>
> > > 2013/06/24 22:03:05 [crit] 34189#0: *1 open()
> > > "/usr/local/etc/nginx/authpw" failed (13: Permission denied)
> > >
> > > # ls -lo ./authpw
--- Original message ---
From: "Reinis Rozitis"
Date: 24 June 2013, 23:00:48
> > 2013/06/24 22:03:05 [crit] 34189#0: *1 open()
> > "/usr/local/etc/nginx/authpw" failed (13: Permission denied)
> >
> > # ls -lo ./authpw
> > -r--r- 1 root www - 50 24 чер 21:58 ./authpw
> >
> > What I ha
2013/06/24 22:03:05 [crit] 34189#0: *1 open()
"/usr/local/etc/nginx/authpw" failed (13: Permission denied)
# ls -lo ./authpw
-r--r- 1 root www - 50 24 чер 21:58 ./authpw
What I have missed?
The error log kind of explains - the auth file is not readable by nginx
user.
Do you have spe
Hi, guys!
I am attempting to secure one subdirectory on the server with
ngx_http_auth_basic_module. Unfortunately, without success.
In log file error:
2013/06/24 22:03:05 [crit] 34189#0: *1 open() "/usr/local/etc/nginx/authpw"
failed (13: Permission denied), client: 111.222.251.165, server: s
26 matches
Mail list logo
