haproxy issue when port bound 9900

[santu1120]

Hi Team

We have a server transport.iiko-phi-z1.com where two webpage running one on port 80 another is 9900 but port 80 opening via haproxy without any issue but port 9900 webpage not opening via haproxy. Please help where is the problem in configuration...haproxy configuration in below...

global chroot /var/lib/haproxy stats socket /run/haproxy/admin.sock mode 660 level admin stats timeout 30s user haproxy group haproxy daemon maxconn 200000

    # Default SSL material locations
    #ca-base /etc/ssl
    #crt-base /etc/ssl/certs

    # Default ciphers to use on SSL-enabled listening sockets.
    # For more information, see ciphers(1SSL).
    #ssl-default-bind-ciphers kEECDH+aRSA+AES:kRSA+AES:+AES256:RC4-SHA:!kEDH:!LOW:!EXP:!MD5:!aNULL:!eNULL

defaults option dontlognull mode http option http-no-delay option forceclose maxconn 200000 timeout connect 5s timeout client 600s timeout server 600s timeout http-keep-alive 10s timeout http-request 15s timeout tarpit 1m

frontend http-in bind *:80

Define hosts

acl iiko_biz hdr_beg(host) -i iiko_biz.iiko-phi-z1.com

Define backend

use_backend iiko_biz_server_80 if iiko_biz

capture request header User-Agent len 50 capture request header Content-Length len 50 capture response header User-Agent len 50

frontend http-in_9900 bind 0.0.0.0:9900 mode tcp no option http-no-delay

Define hosts

acl 16804.mena-are hdr_beg(host) -i 16804.mena-are.iiko-phi-z1.com acl iiko_biz hdr_beg(host) -i iiko_biz.iiko-phi-z1.com

    use_backend iiko_biz_server_9900 if iiko_biz

    capture request header User-Agent len 50
    capture request header Content-Length len 120
    capture response header Content-Length len 120

----------------------------------------------------------

backend iiko_biz_server_80 server iiko_biz_server_80 transport.iiko-phi-z1.com:80

backend iiko_biz_server_9900 server iiko_biz_server_9900 transport.iiko-phi-z1.com:9900

=====================================

[tifayuki]

@santu1120

This is like an HAProxy config file issue. Not related to this repo, no?