# Am I misconfiguring the load balancer?

**URL:** <https://forums.suse.com/t/am-i-misconfiguring-the-load-balancer/5406>\
**Category:** General\
**Created:** [February 3, 2017, 3:21pm UTC](https://forums.suse.com/t/am-i-misconfiguring-the-load-balancer/5406 "2017-02-03T15:21:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bkuhl](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bkuhl/32/233_2.png) [@bkuhl](https://forums.suse.com/u/bkuhl)\
**Post date:** [February 3, 2017, 3:21pm UTC](https://forums.suse.com/t/am-i-misconfiguring-the-load-balancer/5406/1 "2017-02-03T15:21:39Z")

</div>

I’m having trouble getting a simple redirect to work on the load balancer. It’s very possible I missed something silly but could use a 2nd pair of eyes.

 ![](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/b/bf22a417c2b53a730fad9a2217b8faabcd356e4f.png)

`stats-and-archives-asp-site` is the primary [mysite.com](http://mysite.com) site and is hosted outside of rancher. My objective is to use Rancher for SSL termination so requests are still served from the primary asp-based site. This target has a health check on it which is passing.

When I visit the root domain (which I’ve modified my local `/etc/hosts` to point to the load balancer) I see a 503 as if the load balancer isn’t seeing the request.

Anyone have any ideas on what I should look at?

---

<div class="post-metadata">

**Author:** ![VAdamec](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vadamec/32/2115_2.png) [@VAdamec](https://forums.suse.com/u/VAdamec)\
**Post date:** [February 3, 2017, 7:29pm UTC](https://forums.suse.com/t/am-i-misconfiguring-the-load-balancer/5406/2 "2017-02-03T19:29:34Z")

</div>

Balancer (HAproxy) use healthcheck, did you setup stats-and-archives-asp-site as a external service with healthcheck ? As fast check you can setup HAproxy to show statistics, add this to haproxy configuration:

```auto
listen stats 
bind 0.0.0.0:9000
mode http
stats enable
stats hide-version
stats realm Haproxy\ Statistics
stats uri /haproxy_stats

```

and then add service rule, TCP port 9000 with lb as a target. Then you can access :9000/haproxy\_stats to see status of frontends and backends (check healthcheck status).

---

<div class="post-metadata">

**Author:** ![bkuhl](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/bkuhl/32/233_2.png) [@bkuhl](https://forums.suse.com/u/bkuhl)\
**Post date:** [February 10, 2017, 4:32pm UTC](https://forums.suse.com/t/am-i-misconfiguring-the-load-balancer/5406/3 "2017-02-10T16:32:09Z")

</div>

Thanks for following up! I just had time to get around to this. It looks like the ip address I’m redirecting to is shown as down within the ha proxy stats. However the Rancher api shows that external service as being healthy:

```auto

"healthCheck": {
"type": "instanceHealthCheck",
"healthyThreshold": 2,
"initializingTimeout": 60000,
"interval": 2000,
"name": null,
"port": 80,
"reinitializingTimeout": 60000,
"requestLine": "GET \"/Archives.aspx?VSN=BBX\" \"HTTP/1.0\"",
"responseTimeout": 2000,
"strategy": "recreate",
"unhealthyThreshold": 3
},
"healthState": "healthy",
"hostname": null,
"instanceIds": null,
"kind": "externalService",

```

 ![](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/3/304f0d536ea5ff360c8654acbecac39561ccf8a1.png)

---

<div class="post-metadata">

**Author:** ![VAdamec](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vadamec/32/2115_2.png) [@VAdamec](https://forums.suse.com/u/VAdamec)\
**Post date:** [February 12, 2017, 7:18am UTC](https://forums.suse.com/t/am-i-misconfiguring-the-load-balancer/5406/4 "2017-02-12T07:18:51Z")

</div>

Hm, that’s strange, if you point cursor to last check text popup window with last state should be visible (probably something like reset). You can enable haproxy logging, if you have syslog server it’s easy, also you can setup something like this [https://github.com/outstand/docker-syslog-ng-stdout](https://github.com/outstand/docker-syslog-ng-stdout) (sidekick container with rsyslog)