Tag Info

New answers tagged

1

The message not responding (recovering) indicates that the server is not responding because it is recovering from a failover (or initial start). And is probably still populating the lease databases with all of the free leases from your pool, which could take a while if you have a large pool. Try with a smaller pool to verify your failover is working ...


0

Fleet does not directly interact with load balancers. You could use a "presence" container as described in the example at https://coreos.com/docs/launching-containers/launching/fleet-example-deployment/ to manage an ELB.


1

NLB heartbeats operate at Layer 2, so no firewall ports need to be opened. Here's a screenshot of an NLB heartbeat, captured with Microsoft Network Monitor:


2

NLB operates at the Ethernet layer, which is below the whole TCP/IP stack and thus below any firewall. And, anyway, NLB hosts must be connected to the same network segment: there can't possibly be any block between them.


1

Thanks for all suggestions, but noe of them matched. I have no idea why the observed and decribed pattern of malfunction (and temporal development of malfunction) occured, but the culprit is hidden in what I described as Tons of windows updates It's KB3002567. An update that soon after its release became known as "breaking RDP" - or in fact ...


0

you can proxy by using the rtmp module in the dmz and adding applications with the same name as another rtmp server application myVideos { live on; pull rtmp://<ip address>/myVideos; }


0

Sounds to me like you need to change the RD Session Host server's certificates so that they match the farm name. Basically, you need to get your CA to issue you a certificate who's CN is the farm's FQDN , and who's SAN entries contain the FQDN for each server in the farm as well as the farm FQDN again. The process is outlined here, but that assumes you ...


1

It seems rather difficult to find the needle in the haystack here, but I believe this is a configuration error somewhere. Following this should give you a working baseline configuration: create A-RRs in the DNS zone for <domain> for <farmname.domain> pointing to each of your session hosts in the farm set up trusted certificates for each ...


2

I believe that F5 and AWS have partnered to offer a product. The F5 VE will allow you to use ratio load balancing. This load balancer software may be purchased on a yearly subscription or hourly basis as needed.


4

An SSL certificate depends on the IP address of host too, right (besides the hostname)? No, only the Hostname ("DNS-Name") is relevant for a X.509 certificate and the Application Layer. Such a certificate has a field called Common Name (CN) which holds the domain name (which also apprears in the address bar of your browser). The browser validates the ...


0

I managed to accomplish this using an approach like the one described here: http://scottwb.com/blog/2013/10/28/always-on-https-with-nginx-behind-an-elb/. In NGINX config, I added: A specific location directive for the healthcheck URL ("/healthcheck") that does not do any HTTPS enforcement. A redirect if the "X-Forwarded-Proto: https" header does not ...


2

Load Balancing is the best option. Nginx, haproxy, apache, etc. support load balancing / reverse proxy based on the url path. Layer 7 Load Balancing with HAproxy Reverse Proxy with Nginx


1

Can't do wildcards AFAIK, but you can just match the tail of the address, which should do the same thing: acl match_tail_example hdr_end(host) -i .demo.site.net


2

The problem is in the load balancing implementation. It simply balances load to both uplinks, without taking care that TCP connections from source X to destination Y always use the same WAN interface. You need to configure your load balancer to perform load balancing based on source IP / destination IP pairs, so that a single pair is always sent out via the ...


2

Remove the http { .. } and just have this inside your /etc/nginx/sites-available/default: upstream myapp1 { server 192.168.0.20; } server { listen 80; location / { proxy_pass http://myapp1; } }


1

you will need to send HOST: header to your upstream server IP's also this artical is fully ansering to question Make nginx to pass hostname of the upstream when reverseproxying also you nginx config should looks like this upstream serverpool { server 1.2.3.101:80 weight=1; server 1.2.3.102:80 weight=1; } server { listen 80; server_name ...


1

You should almost always set Host header. Otherwise nginx falls back to default proxy_set_header Host $proxy_host; which in your case would be serverpool which is useless for apache. See http://nginx.org/r/proxy_set_header and http://nginx.org/r/proxy_pass for details. upstream serverpool { server 1.2.3.101:80 weight=1; server 1.2.3.102:80 weight=1; } ...


0

HTTPs traffic can generate a very high load due to the encryption requirements. They make add-in cards which allow you to offload SSL encryption/decryption to specifically designed hardware. As mentioned above, you can terminate SSL on a load balancer which will reduce costs because (at least for the F5) these devices come with this SSL offload equipment. ...


0

This depends on whether you are using Source Address Translation or not. If you use this feature, it will show the BIG-IP's self-IP. Otherwise it will show the origional source address.


1

In this situation, on the very first HTTP request, you will never log the correct persistence entry based on the above iRules. The reason for this is that persistence is set in another event later on because the F5 has not yet decided which pool member this request will be load balanced to. Since this decision has not been made, it is impossible to create ...


0

This sounds like you may need to configure persistence. What can happen in this situation is that you will login to back end server A) and then on future requests end up connected to server B). You never logged into server B) and you get redirected back to the login page. This clobbers the login data in the local browser for server A) when you log in to ...


0

F5 can't natively support queries directly against a database. As such, this may be why you are having an issue. You may want to look into external health monitors


0

The software functions much like a Red Hat subscription - the support and current software version are a package deal. Typically the yearly subscription is not cheap costing upwards of several thousand dollars. That being said, you do get what you pay for. The support is world class as Brian mentioned (the sales guys as you discovered maybe not so much) and ...


2

The reason this is occurring is because when the client connects, it establishes a connection to a specific back end server and the F5 will send all subsequent requests using that same connection as long as it exists. When dealing with typical client web requests from human users this solves a bunch of problems and is typical behavior. This behavior ...


0

If a 500 error occurs, this indicates a problem on the web server. The F5 will then simply forward this error along to the connecting client. It will not "re-send" the request of it's own accord. The only way this could happen is if the client re-tries the request. At that point, this request could possibly be load balanced to another pool member, though ...



Top 50 recent answers are included