Bug #7987


Haproxy Widget: Missing Actions Button

Added by Kilian Ries over 6 years ago. Updated over 6 years ago.

Not a Bug
Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:



already opened a thread in the pfsense forum some weeks ago:

I'm missing the action button (activate / deactivate a backend) in the haproxy widget. In an older version, i can still see it and activate / deactivate my backends (screenshots).



Actions #1

Updated by Kill Bill over 6 years ago

There is no information to debug your issue, neither here, not on the forums. A cut off screenshot doesn't really cut it :-P People need configuration for reproducing the issue.

Actions #2

Updated by Kilian Ries over 6 years ago

Here is my haproxy configuration:

# Automaticaly generated, dont edit manually.
# Generated on: 2017-10-13 09:38
    maxconn            1000
    log            /var/run/log    local0    info
    stats socket /tmp/haproxy.socket level admin
    uid            80
    gid            80
    nbproc            1
    chroot            /tmp/haproxy_chroot
    tune.ssl.default-dh-param    2048
    server-state-file /tmp/haproxy_server_state
    spread-checks 5

listen HAProxyLocalStats
    bind name localstats
    mode http
    stats enable
    stats refresh 10
    stats admin if TRUE
    stats uri /haproxy/haproxy_stats.php?haproxystats=1
    timeout client 5000
    timeout connect 5000
    timeout server 5000

frontend dev-HTTP
    bind            217.33.xx.xx:80 name 217.33.xx.xx:80   
    bind            2001::xx:80 name 2001::xx:80   
    mode            http
    log            global
    option            http-server-close
    option            forwardfor
    acl https ssl_fc
    http-request set-header        X-Forwarded-Proto http if !https
    http-request set-header        X-Forwarded-Proto https if https
    timeout client        60000
    default_backend dev-HTTP-nodeport_http_ipvANY

frontend dev-HTTPS
    bind            217.33.xx.xx:443 name 217.33.xx.xx:443   
    bind            2001::xx:443 name 2001::xx:443   
    mode            tcp
    log            global
    maxconn            20000
    timeout client        300000
    default_backend dev-HTTPS-nodeport_tcp_ipvANY

backend dev-HTTP-nodeport_http_ipvANY
    mode            http
    log            global
    balance            roundrobin
    timeout connect        60000
    timeout server        60000
    retries            3
    server            dev01.intern 192.168.xx.xx:31080 check inter 1000  
    server            dev02.intern 192.168.xx.xx:31080 check inter 1000  

backend dev-HTTPS-nodeport_tcp_ipvANY
    mode            tcp
    log            global
    balance            roundrobin
    timeout connect        300000
    timeout server        300000
    retries            3
    server            dev01.intern 192.168.xx.xx:31443 check inter 1000  send-proxy 
    server            dev02.intern 192.168.xx.xx:31443 check inter 1000  send-proxy
Actions #3

Updated by Jim Pingle over 6 years ago

  • Category set to haproxy
  • Status changed from New to Not a Bug

If the actions column is missing, your user does not have access to "WebCfg - Services: HAProxy package" so it does not have sufficient privileges to control the haproxy process.

Actions #4

Updated by Kilian Ries over 6 years ago

I'm working as admin in the pfsens gui - that account should have enough privileges, or?

Actions #5

Updated by Jim Pingle over 6 years ago

Please discuss the problem on the forum. You probably have unintentionally made a change to your users or groups which broke their privileges.

Actions #6

Updated by Kilian Ries over 6 years ago

Thanks Jim, your hint was right! I'm not shure how this could happen (maybe through an update ...) but the admin user was not part of the admin group! Strange ... readded to the right group and it is working as before now!



Also available in: Atom PDF