Having one block per server is the best for performance because you only test a condition once; the way you're doing it would require NGINX to evaluate hostnames twice or maybe more. In my opinion config maintenance is important as well so either stick to what you have (unless those sites have thousands of requests per second) or generate the configs using Puppet, Chef or the like... Sent froby unai - Nginx Mailing List - English
Johannes, Is this what you are asking for? # cat /etc/nginx/sites-enabled/site1 server { listen 80; server_name subdomain1.domain.com # config... } # cat /etc/nginx/sites-enabled/site2 server { listen 80; server_name subdomain2.domain.com # config... } .... # cat /etc/nginx/sites-enabled/siteN server { listen 80; server_nby unai - Nginx Mailing List - English
Sure, you are very welcome, take care Unai Rodriguez CTO & Cofounder LeanWired LLP Singapore 168977 www.leanservers.com unai@leanservers.com On 5 Jan, 2012, at 17:14, "DeneB" <nginx-forum@nginx.us> wrote: > Forms are writing to the database! Thanks Unai, and have a great day! > > Posted at Nginx Forum: http://forum.nginx.org/read.php?2,220816,220828#msg-220828 &gby unai - Nginx Mailing List - English
Do you get the error "502 bad gateway" with any PHP page? It seems PHP might not be working at all. I would recommend creating a very simple PHP page and testing if it works with the following content for example: <?php phpinfo(); ?> Let us know if this works. -- Unai Rodriguez CTO & Cofounder LeanWired LLP Singapore 168977 www.leanservers.com unai@leanservers.com Onby unai - Nginx Mailing List - English
Fxofxo, What do you mean by "nothing happened, nginx failed"? Is there any specific error on the logs? Are you sure NGINX is being restarted properly? Is NGINX listening on port 82 after you restart it? Unai Rodriguez CTO & Cofounder LeanWired LLP Singapore 168977 www.leanservers.com unai@leanservers.com On 5 Jan, 2012, at 3:05, "fxofxo" <nginx-forum@nginx.us> wrotby unai - Nginx Mailing List - English
Vuki, You could use the Auth PAM module: http://web.iti.upv.es/~sto/nginx/ Unai Rodriguez CTO & Cofounder LeanWired LLP Singapore 168977 www.leanservers.com unai@leanservers.com On 28 Dec, 2011, at 14:59, Vuki <szun@informatik.hu> wrote: > Hi All! > > Is it possible to set up http auth against linux users (/etc/passwd)? > > thx > > ___________________________by unai - Nginx Mailing List - English
Hey Atrus, I thought that article was relevant and was just checking if you read it. It looked like a very similar scenario to yours. And what is your point ? > > Atrus@ > > Posted at Nginx Forum: > http://forum.nginx.org/read.php?2,220365,220373#msg-220373 > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.ngby unai - Nginx Mailing List - English
Jeff, Thanks. > I just need the incoming data to the second server for testing and > analyzing, since the original-server is in production environment. > > All the servers are Ubuntu Linux 9.10 OS. > > _______________________________________________ > nginx mailing list > nginx@nginx.org > http://mailman.nginx.org/mailman/listinfo/nginx > I have never seen/encounterby unai - Nginx Mailing List - English
Have you seen this link? http://www.remsys.com/nginx-on-1gbps On Thu, Dec 22, 2011 at 3:00 PM, atrus <nginx-forum@nginx.us> wrote: > Guys !! > Is there anybody help me overcomes this ? > > Posted at Nginx Forum: > http://forum.nginx.org/read.php?2,220365,220369#msg-220369 > > _______________________________________________ > nginx mailing list > nginx@nginx.orgby unai - Nginx Mailing List - English
Jeff, I can't think of a (simple) way of doing this through NGINX. It seems to me that the simplest might be to handle this on iptables (are you using Linux?) directly by setting up something similar to what's covered here: http://www.bjou.de/blog/2008/05/howto-copyteeclone-network-traffic-using-iptables/ so your destination would be some sort of an alias that actually represents 2 destinationby unai - Nginx Mailing List - English
I have the following simple server block on NGINX: server { listen 80; listen 8090; server_name st.rdsx.net; autoindex on; root /home/users/saifbechan/st-rdsx-net; } After I include the relevant settings on my hosts file I get the following (unexpected) behavior: (1) http://st.rdsx.net/ and http://st.rdsx.net:8090/ work fine; (2) http:by unai - Nginx Mailing List - English