Bobcares

HAProxy Bind Multiple Ports: How to?

by | Apr 29, 2023

Let us learn how to setup the haproxy bind multiple ports with the support of our Server management support services at Bobcares.

Why setup the HAProxy bind multiple ports?

When HAProxy connects to several ports, it listens on each port for incoming traffic and routes it to the appropriate backend server based on the configuration.

This can be beneficial in a variety of contexts, including load balancing web applications that require various ports for distinct services or enabling access to several services via a single IP address.

How to configure HAProxy to bind to multiple ports?

  1. Configure the frontend:

    We must first configure the frontend in the HAProxy configuration file. HAProxy’s frontend defines the IP address and port on which it will listen for incoming traffic.

    To configure multiple ports, just add additional “bind” lines to the frontend settings, one for each port number. As an example:

    In this example, we set HAProxy to listen on three separate ports: port 80 for HTTP traffic, port 443 for HTTPS communication, and port 8080 for all other sorts of traffic. Now move to the next step in setting up HAProxy bind multiple ports.

  2. Configure the backend:

    After configuring the frontend, you must setup the backend to define which backend servers will accept traffic from each port. We can accomplish this by including “use_backend” lines in the frontend configuration, which define the backend server to use for each port.

    .

    Example:

    In this example, we set HAProxy to use the “mybackend_http” backend for HTTP traffic on port 80, the “mybackend_https” backend for HTTPS traffic on port 443, and the “mybackend_other” backend for all other forms of traffic on port 8080.

  3. Configure the backend servers:

    Finally, we must configure the backend servers that will receive traffic from each port. In the backend setup, give the IP address and port of each backend server. As an example:

    This example supplies the IP address and port number for each backend server. However, using the “ssl verify none” option to deactivate SSL verification for HTTPS traffic is not recommended for production applications.

  4. Configure ACLs (Optional):

    You can also use access control lists (ACLs) to further customize the routing of incoming requests. For instance, ACLs enable you to redirect requests based on the URL, host header, or other criteria.

    An ACL that routes requests depending on the URL is shown below:

    The system will use the “blog_backend” backend to distribute traffic if the incoming request route starts with “/blog.” Otherwise, it will utilize the “main_backend” backend.

  5. Restart HAProxy:

    Finally, we must restart the HAProxy service in order for the new configuration to take effect. This may be accomplished by issuing the following command:

    sudo service haproxy restart

    We may listen for incoming traffic on several network interfaces and distribute it to the appropriate backend servers based on the configuration by binding to numerous ports in HAProxy.

[Need assistance with similar queries? We are here to help]

Conclusion

To sum up we have now seen how to setup the haproxy bind multiple ports with the support of our tech team.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF