# Bug in deriving the backend port!

**URL:** https://discourse.haproxy.org/t/bug-in-deriving-the-backend-port/109
**Category:** Help!
**Created:** [February 13, 2016, 10:12am UTC](https://discourse.haproxy.org/t/bug-in-deriving-the-backend-port/109 "2016-02-13T10:12:37Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![ajithflex](https://avatars.discourse-cdn.com/v4/letter/a/f07891/32.png) [@ajithflex](https://discourse.haproxy.org/u/ajithflex)
#### Post date: [February 13, 2016, 10:12am UTC](https://discourse.haproxy.org/t/bug-in-deriving-the-backend-port/109/1 "2016-02-13T10:12:37Z")

</div>

I am not sure if this is the right platform to report this.  
haproxy tries to use the “source\_port” as the “destination\_port” in my configuration. This happens when my frontend listens on multiport. Its reproducible in 1.6 stable version as well.

---

<div class="post-metadata">

### Author: ![Baptiste](https://avatars.discourse-cdn.com/v4/letter/b/cab0a1/32.png) [@Baptiste](https://discourse.haproxy.org/u/Baptiste)
#### Post date: [February 15, 2016, 5:16pm UTC](https://discourse.haproxy.org/t/bug-in-deriving-the-backend-port/109/2 "2016-02-15T17:16:13Z")

</div>

maybe you could share your configuration 🙂