# Load balancer reverse proxy to services

**URL:** <https://forums.suse.com/t/load-balancer-reverse-proxy-to-services/7603>\
**Category:** Rancher 1.x\
**Created:** [October 17, 2017, 11:59pm UTC](https://forums.suse.com/t/load-balancer-reverse-proxy-to-services/7603 "2017-10-17T23:59:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisreed87](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/chrisreed87/32/2940_2.png) [@chrisreed87](https://forums.suse.com/u/chrisreed87)\
**Post date:** [October 17, 2017, 11:59pm UTC](https://forums.suse.com/t/load-balancer-reverse-proxy-to-services/7603/1 "2017-10-17T23:59:30Z")

</div>

Having an issue with a Load Balancer (haproxy) that we’re trying to get setup for a new stack. My services are up and running on their respective ports (8000 and 8080) and I can curl to get their API responses just fine.

Example: `curl -i http://34.213.188.6:8000/v1/configurations`

However, I’d like the LB to listen on port 80 and proxy to the service running on 8000 so I could just run this…  
`curl -i http://34.213.188.6/go-configuration-agent-api/v1/configurations`,  
…however that just returns a 404

I feel like it’s just something dumb i’m missing in the lb config, or maybe the rancher lb/haproxy isn’t supposed to do this (??)

 ![Screenshot-2017-10-17 Rancher](https://us1.discourse-cdn.com/flex022/uploads/suse/original/2X/a/a161ff730b3ce938db4f41b18da8d463359a5eae.png)

---

<div class="post-metadata">

**Author:** ![shubbard343](https://avatars.discourse-cdn.com/v4/letter/s/47e85d/32.png) [@shubbard343](https://forums.suse.com/u/shubbard343)\
**Post date:** [October 20, 2017, 10:23pm UTC](https://forums.suse.com/t/load-balancer-reverse-proxy-to-services/7603/2 "2017-10-20T22:23:50Z")

</div>

I think the problem might be that when the load balancer sends the requests to the backend service it does not strip out the “go-configuration-agent-api” from the string. If your backend service is expecting to receive the URL /v1/configurations, but the actual url it receives is /go-configuration-agent-api/v1/configurations.
