<div>we might need to see your whole configuration to get the full picture, but here's an initial thought...</div><div><br></div><div>if your apache does virtual hosting based on the Host: header (which seems likely from your description), you may need to pass the Host: header along, which you can do like this:</div>
<div><br></div><div><pre style="margin-top:10px;margin-bottom:10px;background-image:initial;background-color:rgb(255,255,255);border-top-width:1px;border-right-width:1px;border-bottom-width:1px;border-left-width:1px;border-top-style:solid;border-right-style:solid;border-bottom-style:solid;border-left-style:solid;border-top-color:rgb(136,136,136);border-right-color:rgb(136,136,136);border-bottom-color:rgb(136,136,136);border-left-color:rgb(136,136,136);padding-top:3px;padding-right:3px;padding-bottom:3px;padding-left:3px;overflow-x:auto;overflow-y:auto;color:rgb(51,51,51);font-size:12px;line-height:18px;text-align:left">
<code>proxy_set_header Host $http_host;</code></pre></div><div><br></div><div><br></div><div class="gmail_quote">On Tue, Jan 24, 2012 at 10:33 AM, António P. P. Almeida <span dir="ltr"><<a href="mailto:appa@perusio.net">appa@perusio.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 24 Jan 2012 15h26 WET, <a href="mailto:nginx-forum@nginx.us">nginx-forum@nginx.us</a> wrote:<br>
<br>
> Hi, getting quite desperate at the moment about this.<br>
><br>
> I have a server serving several subdomains; actually proxying'em to<br>
> apache2. So I have main nginx vhost file with all server_name's<br>
> added. Such server names match the defined ServerName's and<br>
> ServerAlias'es of Apache. Beside, I have one more file to define a<br>
> default_server catch all block like follows<br>
><br>
> server {<br>
> listen 80 default_server;<br>
> server_name _;<br>
> error_log /var/log/nginx/000default-error.log error;<br>
> root /var/www/<a href="http://forvo.com/_templates" target="_blank">forvo.com/_templates</a>;<br>
> error_page 404 /404.html;<br>
> location / {<br>
> #return 444;<br>
> return 404;<br>
> }<br>
> location = /404.html {<br>
> internal;<br>
> }<br>
> #rewrite .* <a href="http://myfaultysubdomain.com" target="_blank">http://myfaultysubdomain.com</a> permanent;<br>
> }<br>
<br>
</div>AFAICT there's nothing here that should cause the 503s. Do you have<br>
any limits set, be it connection or rate limit?<br>
<span class="HOEnZb"><font color="#888888"><br>
--- appa<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
<br>
<br>
><br>
> As soon as I enable this file, everything works as expected,<br>
> however, in less than one minute (my site is always being visited),<br>
> all requests (good subdomains and bad subdomains as well) start to<br>
> get 503 response. No log at all seems to change when this happens.<br>
><br>
> Any clue to what may be happening pleeeeeease ......it's been hours,<br>
> during days, trying to figure out what the h@$!! is going on<br>
><br>
> Posted at Nginx Forum:<br>
> <a href="http://forum.nginx.org/read.php?2,221572,221572#msg-221572" target="_blank">http://forum.nginx.org/read.php?2,221572,221572#msg-221572</a><br>
><br>
> _______________________________________________<br>
> nginx mailing list<br>
> <a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
> <a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
<br>
_______________________________________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" target="_blank">http://mailman.nginx.org/mailman/listinfo/nginx</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><span style="font-family:arial,sans-serif;font-size:13px;border-collapse:collapse"><span style="color:gray">Will 'Mit' Rowe<br>Stagename</span><i><br>
</i><span style="color:rgb(153,153,153)">1-866-326-3098</span><br><span style="color:rgb(153,153,153)"><a href="mailto:josh@stagename.com" style="color:rgb(42,93,176)" target="_blank">mit@stagename.com</a></span><br style="color:rgb(153,153,153)">
<span style="color:rgb(153,153,153)"><a href="http://www.stagename.com/" style="color:rgb(42,93,176)" target="_blank">www.stagename.com</a></span><br><span style="color:rgb(153,153,153)">Twitter: @stagename</span><br style="color:rgb(153,153,153)">
<br style="color:rgb(153,153,153)"><span style="font-size:8pt;color:rgb(153,153,153)"></span><i><span style="font-size:8pt;color:gray">The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of this information by persons or entities other than the intended recipient is prohibited. If you received this transmission in error, please contact the sender and delete all material contained herein from your computer.</span></i><span style="font-size:8pt;color:gray"></span> </span><br>