# Load Balancer Request Path not working

**URL:** <https://forums.suse.com/t/load-balancer-request-path-not-working/3503>\
**Category:** Rancher 1.x\
**Created:** [July 22, 2016, 10:52am UTC](https://forums.suse.com/t/load-balancer-request-path-not-working/3503 "2016-07-22T10:52:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![polysign](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/polysign/32/1534_2.png) [@polysign](https://forums.suse.com/u/polysign)\
**Post date:** [July 22, 2016, 10:52am UTC](https://forums.suse.com/t/load-balancer-request-path-not-working/3503/1 "2016-07-22T10:52:33Z")

</div>

Hi there,

running Rancher v 1.1.1 on 4 Hosts (1 Rancher + 3 Servers to run the containers on).  
I have a couple of services running and its all great 🙂

I am also running Drone and I was trying to get Drone/Wall to run as well.  
So I created a new service inside the Drone Stack.

So my Drone stack looks like this:

- Drone-Server + 3 Sidekicks = running on Port 8000
- Drone-Wall = running on Port 80

Now I added a load balancer listening on port 80.  
Inside the targets I specified the following:

- [drone.domain.com](http://drone.domain.com) \> 80 \> “” \> drone-server \> 8000
- [drone.domain.com](http://drone.domain.com) \> 80 \> “/wall” \> drone-wall \> 80

Now when I browse to [drone.domain.com](http://drone.domain.com) I see the Drone CI. But when I browse to [drone.domain.com/wall](http://drone.domain.com/wall) I see a 404 page (probably coming from Drone Server).

Did I miss anything?

Thanks  
br

Georges

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [July 22, 2016, 3:49pm UTC](https://forums.suse.com/t/load-balancer-request-path-not-working/3503/2 "2016-07-22T15:49:57Z")

</div>

I’m not familiar with drone wall, but the matching portion of the path is not removed from the request that is sent to the target services. So the request is probably going to the wall container, but it responds with 494 when asked for `/wall`.

Some applications have an option to configue the base URL they are being served out of. Otherwise you’ll have to use host-based-routing. The balancer removing the path from the request to the target would work too load the HTML, but then break any absolute or root-relative links/js/css/images/etc that the application tries to reference.

---

<div class="post-metadata">

**Author:** ![polysign](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/polysign/32/1534_2.png) [@polysign](https://forums.suse.com/u/polysign)\
**Post date:** [July 23, 2016, 7:43pm UTC](https://forums.suse.com/t/load-balancer-request-path-not-working/3503/3 "2016-07-23T19:43:32Z")

</div>

Hi Vincent. This totally makes sense and I wasn’t aware of it. Will see on how to change the configuration of the container to use a different base URL.

Thanks.

br  
Georges