You're right, my solution sucks... but it has the benefit of being generic.
I'll look into it.
Glad you found a solution, though. ;o)
---
*B. R.*
On Mon, May 6, 2013 at 4:19 PM, Aleksandar Lazic wrote:
> **
>
> I remember this and now also where I have seen it ;-)
>
> http://wiki.nginx.org/Pi
Configs :
http://pastebin.com/QDpjDSBY
http://pastebin.com/SyQTmq8v
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238923,238926#msg-238926
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi, I'm using nginx in a reverse proxy setup with 2 apache 2.4 backends,
I've configured a cookie based proxy_pass setup as shown in
http://dgtool.blogspot.com/2013/02/nginx-as-sticky-balancer-for-ha-using.html
, however php header redirects seem to die (or the browser doesn't like)
when nginx go
I remember this and now also where I have seen it ;-)
http://wiki.nginx.org/Pitfalls#Server_Name
Thanks for all feedback.
I will try the Solution written in first post.
Br aleks
Am 06-05-2013 20:30, schrieb B.R.:
> I do:
> if ($host ~* "^www.(.*)$") {
> set "$domain" "$1";
> rewrite (
Hi,
Beside the file cache and ssl sharing sessions, does anyone knows of a 3rd
party module which uses rbtree to store information?
Thanks,
Alex
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238920,238920#msg-238920
___
nginx mailing list
Richard - I ran netcat, but no debug output appeared when running
nginx/mono. I'm not sure if this is a sign of anything or not though? :-(
Jonathan - I tried your chmod suggestion - but still no joy :-(
Any other ideas? *fingers crossed*
Thanks
G
if you REJECT from iptables you tell the client immediatly that the
service/port is not available, otherwise you run into timeouts, yes.
i'm not quite sure, but max_fails=3 x fail_timeout=30s == 90 seconds, until
your nginx fails over to the other
server.
regards,
mex
Posted at Nginx Forum:
Even when explicitly setting the socket option IPV6_V6ONLY to 0
(man 7 ipv6) - and thus ignoring ´cat /proc/sys/net/ipv6/bindv6only´
this doesn't work.
> While looking into this, I found that, when given ::1, nc(1)
> explicitly listens to both ::1 and :::127.0.0.1.
The behavior here is exac
I do:
if ($host ~* "^www\.(.*)$") {
set "$domain" "$1";
rewrite (.*) http://$domain$uri permanent;
}
---
*B. R.*
On Mon, May 6, 2013 at 12:50 PM, Jonathan Matthews
wrote:
> That's how I do it, except that I hard-code a list of the domains I
> want to redirect. Otherwise, I'd have built a
On 6 May 2013 18:47, Gee wrote:
> Hi
>
> I am having trouble getting Mono to work with nginx. I installed my OS
> (OpenBSD 5.3) and set up ports. I built mono, mono-xsp and nginx - all
> without incident. All three appear to be working OK, but not in
> conjunction.
>
> I am trying to run the de
On 06/05/13 18:47, Gee wrote:
The frustrating thing here is that /tmp/fastcgi.socket does actually
exist. I tried 'touch' and making sure 'wheel' has the appropriate
permissions. The result of 'ls -la /tmp/fastcgi.socket' revealed
nothing awry.
Does anyone have any ideas/hints?
To try
> "LT" == Lukas Tribus writes:
LT> Hi Jim,
>> Everything else sees conenctions to anything in 127.0.0.0/8
LT> Not sure what you mean by everything else, but I don't think
LT> thats the case.
Some time ago a message on debian-devel noted that deb was going to start
defaulting to bindv6only=1
Hi
I am having trouble getting Mono to work with nginx. I installed my OS
(OpenBSD 5.3) and set up ports. I built mono, mono-xsp and nginx - all
without incident. All three appear to be working OK, but not in
conjunction.
I am trying to run the default MVC3 web app, but keep getting a 502 (Bad
I didn't even think about rejecting the traffic rather than dropping it!
Great idea!
Would that allow the client connection (Browser to Nginx) to fail over to
the backend server that is up rather than simply timing out?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,238894,238913#msg-2
Hi Jim,
> Everything else sees conenctions to anything in 127.0.0.0/8
Not sure what you mean by everything else, but I don't think
thats the case.
See this example:
> lukas@ubuntuvm:~$ grep Listen /etc/ssh/sshd_config
> ListenAddress ::1
> ListenAddress 10.0.0.55
> lukas@ubuntuvm:~$ sudo netst
That's how I do it, except that I hard-code a list of the domains I
want to redirect. Otherwise, I'd have built a service that could be
trivially used by anyone else for their own domain. Wildcards are bad,
mmkay? ;-)
IMHO and YMMV,
Jonathan
___
nginx m
I just do
server {
listen 80;
server_name was.foo.com;
rewrite ^ http://foo.com$uri permanent;
}
On May 6, 2013, at 9:40 AM, Aleksandar Lazic wrote:
> Dear readers,
>
> after reading
>
> http://nginx.org/en/docs/http/server_names.html#regex_names
>
> and googleing
>
> https://www.
Dear readers,
after reading
http://nginx.org/en/docs/http/server_names.html#regex_names
and googleing
https://www.google.at/search?q=nginx+remove+www+subdomain
I have a 'best solution' question.
I have the following customer request.
The 'normal User' type almost every time a www.subdomain.
Hello!
On Mon, May 06, 2013 at 12:12:44PM -0400, mevans336 wrote:
> Hi Mex,
>
> We shut them down one-by-one, 45 minutes apart. The issue only seems to
> occur when the first server listed is blocked however. We don't see the read
> timeouts if I leave the iptables rules enabled on the second se
If this is a linux box you could simple use [::]:80 and it should, by
default, responde to both v4 and v6...
"In Linux by default any IPv6 TCP socket also accepts IPv4 traffic using
the IPv4 to IPv6 mapped address format, i.e., :::. E.g., :::192.168.0.27 maps the IPv4 address
192.168.0.27
> "LT" == Lukas Tribus writes:
>> Although [::]:80 ipv6only=off; does work as advertized (including for
>> localhost sockets), [::1]:80 ipv6only=off; fails to respond to v4
>> connections.
LT> Which is expected, since ::1 is an ipv6 address.
No it is not expected.
Everything else sees cone
Oops, here is the relevant error.log entry from Nginx as well:
013/05/06 01:46:03 [error] 2063#0: *294659 upstream timed out (110:
Connection timed out) while connecting to upstream, client: ip.address,
server: amywebsite.com, request: "GET /home HTTP/1.1", upstream:
"http://192.168.1.12:8080/home
Hi Mex,
We shut them down one-by-one, 45 minutes apart. The issue only seems to
occur when the first server listed is blocked however. We don't see the read
timeouts if I leave the iptables rules enabled on the second server. I think
that may be a false symptom related to ip_hash binding clients t
Hello Steve, yeah i took out ( :
Everything is working fine!
now am starting to dig the cache module, so my backend doesnt get called
too many times in a short period of time..
thanks a lot guys for all your help ( :
On Monday, 6 May 2013, Steve Holdoway wrote:
> On Mon, 2013-05-06 at 00:14 +0
On 05/06/13 09:54, Maxim Dounin wrote:
Hello!
On Mon, May 06, 2013 at 09:01:45AM -0400, Jim Ohlstein wrote:
On 05/05/13 16:32, Maxim Dounin wrote:
Hello!
On Sat, May 04, 2013 at 07:08:55PM -0400, Jim Ohlstein wrote:
[...]
I have just seen a similar situation using fastcgi cache. In my cas
mex Wrote:
---
> ehlo,
>
>
> one question: do you shutdown all your app-servers or
> server-by-server, so you still have a available application?
my bad, please read:
do you shutdown all your app-servers at once or
server-after-server, so you
Hello!
On Mon, May 06, 2013 at 09:31:14AM -0400, nevernet wrote:
> i have resolver define, see below configuration:
>
> server {
> listen 80;
> server_name xx.com;
> access_log /var/log/nginx/xx-nginx.access.log;
> error_log /var/log/nginx/xx-nginx_error.log debug;
>
> # resolver 8.8.8
ehlo,
one question: do you shutdown all your app-servers or server-by-server, so
you still have
a available application?
there ist the "down" option for you upstream-block to disable servers, even
if they are
up, but using this in a dynamic process might get very frickling.
whet do you use f
Hello!
On Mon, May 06, 2013 at 09:01:45AM -0400, Jim Ohlstein wrote:
> On 05/05/13 16:32, Maxim Dounin wrote:
> >Hello!
> >
> >On Sat, May 04, 2013 at 07:08:55PM -0400, Jim Ohlstein wrote:
> >
> >[...]
> >
> >>I have just seen a similar situation using fastcgi cache. In my case
> >>I am using the
Hi!
> how to disable nginx internal dns cache?
Use an IP address instead of a hostname in the proxy_pass variable.
> both of them doesnt work.
Can you elaborate what "it doesn't work" mean?
Lukas
___
nginx m
Hello,
Each night we take our backend servers offline at specific times for
maintenance. When the application servers restart they immediately begin
answering HTTP requests from Nginx, but we want to keep them out of the
upstream pool for about 30 minutes while they cache information from our
data
i have resolver define, see below configuration:
server {
listen 80;
server_name xx.com;
access_log /var/log/nginx/xx-nginx.access.log;
error_log /var/log/nginx/xx-nginx_error.log debug;
# resolver 8.8.8.8;
# resolver_timeout 1s;
#set your default location
location / {
# resolver 8.8
On 05/05/13 16:32, Maxim Dounin wrote:
Hello!
On Sat, May 04, 2013 at 07:08:55PM -0400, Jim Ohlstein wrote:
[...]
I have just seen a similar situation using fastcgi cache. In my case
I am using the same cache (but only one cache) for several
server/location blocks. The system is a fairly basi
Recently, I updated nginx from 1.0.15 to 1.2.8, and find that the
ports(shown by ss -s) increase much as below:
nginx/1.0.15
Total: 21696 (kernel 22773)
TCP: 111474 (estab 21422, closed 86149, orphaned 3803, synrecv 0, timewait
86145/0), ports 1417
nginx/1.2.8
Total: 21579 (kernel 22349)
TCP:
34 matches
Mail list logo
