# Bind "name" parameter seems to be ignored

**URL:** <https://discourse.haproxy.org/t/bind-name-parameter-seems-to-be-ignored/486>\
**Category:** Help!\
**Created:** [July 7, 2016, 1:48pm UTC](https://discourse.haproxy.org/t/bind-name-parameter-seems-to-be-ignored/486 "2016-07-07T13:48:48Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sottolski](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@sottolski](https://discourse.haproxy.org/u/sottolski)\
**Post date:** [July 7, 2016, 1:48pm UTC](https://discourse.haproxy.org/t/bind-name-parameter-seems-to-be-ignored/486/1 "2016-07-07T13:48:48Z")

</div>

Howdy,

I’m trying to condense my configruation for 1.6.6 a bit. Instead of

```
frontend FE-1
    bind 172.17.1.11:443 ssl crt /etc/ssl/private/mycert.pem
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

frontend FE-2
    bind 172.17.1.12:443 ssl crt /etc/ssl/private/mycert.pem
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

frontend FE-3
    bind 172.17.1.13:443 ssl crt /etc/ssl/private/mycert.pem
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

```

I thought I could do something like

```
frontend SSL
    bind 172.17.1.11:443 ssl crt /etc/ssl/private/mycert.pem name FE-1
    bind 172.17.1.12:443 ssl crt /etc/ssl/private/mycert.pem name FE-2
    bind 172.17.1.13:443 ssl crt /etc/ssl/private/mycert.pem name FE-3
    reqadd "X-Forwarded-Proto: https"
    default_backend app-servers

```

The docs tell me

> name
> 
> ```
> 
> ```
> 
> Sets an optional name for these sockets, which will be reported on the stats  
> page.

However, I seem not the see any of may names on the stats page.

 ![](https://us1.discourse-cdn.com/flex016/uploads/haproxy/original/1X/f662c2062f688e55123c81f4117fde13b2af2b3b.png)

Is it a misunderstanding on my side what the name is for, or may it be a bug?

Thanks

Sascha

---

<div class="post-metadata">

**Author:** ![willy](https://avatars.discourse-cdn.com/v4/letter/w/c2a13f/32.png) [@willy](https://discourse.haproxy.org/u/willy)\
**Post date:** [July 13, 2016, 8:29am UTC](https://discourse.haproxy.org/t/bind-name-parameter-seems-to-be-ignored/486/2 "2016-07-13T08:29:49Z")

</div>

The problem is not that the name is ignored, but that the individual listening socket doesn’t show up. You need to have “option socket-stats” in your frontend if you want each bind line to appear on the stats page. The doc for “name” would need to be updated to specificly refer to this option in my opinion, feel free to send a patch to the mailing list!

---

<div class="post-metadata">

**Author:** ![sottolski](https://avatars.discourse-cdn.com/v4/letter/s/a698b9/32.png) [@sottolski](https://discourse.haproxy.org/u/sottolski)\
**Post date:** [July 13, 2016, 11:54am UTC](https://discourse.haproxy.org/t/bind-name-parameter-seems-to-be-ignored/486/3 "2016-07-13T11:54:42Z")

</div>

Excellent and useful, thanks a lot. Proposal for configuration.txt:

```
--- git.haproxy.org.txt 2016-07-13 13:45:19.210366893 +0200
+++ configuration.txt 2016-07-13 13:50:56.539746982 +0200
@@ -5969,6 +5969,9 @@
 no option socket-stats
 
   Enable or disable collecting & providing separate statistics for each socket.
+ Note: see also bind parameter "name" in section 5.1 to give each socket a
+ meaningul, well, name.
+
   May be used in sections : defaults | frontend | listen | backend
                                  yes | yes | yes | no
 
@@ -9818,7 +9821,7 @@
 
 name <name>
   Sets an optional name for these sockets, which will be reported on the stats
- page.
+ page. Requires "option socket-stats", see section 4.2.
 
 namespace <name>
   On Linux, it is possible to specify which network namespace a socket will

```

Best

Sascha