Re: Transforming nginx for Windows

standard practice when I don't have lots of resources for > servers. > > Thanks, > > Tony > > Posted at Nginx Forum: > http://forum.nginx.org/read.php?2,242426,248937#msg-248937 > > ___ > nginx mailing list > n

Re: Launching Excel in a production web server on a Mac

in user, and that's simpler since that process only needs to communicate via local sockets. -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Launching Excel in a production web server on a Mac

uld corrupt the old emulation layer so completely that it would not run at all until you rebooted the server (even killing and restarting the "blued" stuff would not do it). Enjoy yourself; I sure as hell did not ;-) -- Scott Ribe scott_r...

Re: Quick performance deterioration when No. of clients increases

a different one. Sorry for the noise. -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Quick performance deterioration when No. of clients increases

u have configured things that way...) -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: We're sorry, but something went wrong

R's exception handling is returning that page to nginx. So I know exactly what to do ;-) -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org

We're sorry, but something went wrong

So I'm in the early stages of rolling out a system to production, and a few app errors are cropping up that didn't get caught in testing, and it occurs to me: it would be nice if the default "we're sorry, but something went wrong" error page could include a timestamp

Re: connect() to 127.0.0.1:80 failed (99: Cannot assign requested address

ow and that's why you're assuming you know what we mean by "run php" or "echo text"...) -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: connect() to 127.0.0.1:80 failed (99: Cannot assign requested address

l getting the error as mentioned in subject > > > On Sun, Jul 14, 2013 at 4:27 AM, Scott Ribe > wrote: > From nginx to something upstream? (That's what I meant.) > > On Jul 13, 2013, at 4:54 PM, Atul Bansal wrote: > > > ya > > > > > > On Su

Re: connect() to 127.0.0.1:80 failed (99: Cannot assign requested address

>From nginx to something upstream? (That's what I meant.) On Jul 13, 2013, at 4:54 PM, Atul Bansal wrote: > ya > > > On Sun, Jul 14, 2013 at 4:22 AM, Scott Ribe > wrote: > On Jul 13, 2013, at 4:48 PM, Atul Bansal wrote: > > > The log error that i am gettin

Re: connect() to 127.0.0.1:80 failed (99: Cannot assign requested address

On Jul 13, 2013, at 4:48 PM, Atul Bansal wrote: > The log error that i am getting is when I try to run any php file in my > browser. Are you trying to pass requests to PHP over port 80? -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567

Re: problem setting up certificate

3, at 12:40 PM, Scott Ribe wrote: > I'm getting this error after installing the certificate & key: > > [emerg] 809#0: SSL_CTX_use_PrivateKey_file("/paging/site/config/server.key") > failed (SSL: error:0B080074:x509 certificate > routines:X509_check_private_key:ke

problem setting up certificate

rted over with a new csr, thinking I had screwed up and used the wrong key or something), and am still getting the error. I've double-checked to make sure that nginx is using the config file I expect, and that it specifies the correct locations for the cert & key. How should I proceed in