New answers tagged

0

I managed to convert the HAProxy session cookie to persistent cookie using Google Tag Manager. Since GTM available in both applications, I just need to create javascript code to convert the cookie to persistent cookie. Here is the code that I put in GTM: <script type="text/javascript"> (function() { function setCookie(cname, cvalue, exdays) { ...


0

I also setup haproxy (2016-05) and in the log i got the error ssl/1: SSL handshake failure It seems ssh v2 waits for the server before talking, causing haproxy to mistake it for a ssl connection. The fix was adding the following lines to ~/.ssh/config Host my.host.com HostName my.host.com Port 443 User MeMe ProxyCommand openssl s_client -connect ...


5

Foreword Update in 2016. Things are evolving, all servers are getting better, they all support SSL and the web is more amazing than ever. Unless stated, the following is targeted toward professionals in business and start-ups, supporting thousands to millions of users. These tools and architectures require a lot of users/hardware/money. You can try this ...


0

Introduction 64k concurrent IDLE connections is peanuts for HAProxy and Erlang. The first thing to do is enable the statistics page on HAProxy. It is a MUST have for monitoring and performance tuning. Then let's get into limits. The OS Connection Limit There can only be 1 connection per tuple client_IP:client_PORT:server_IP:server_PORT. It comes from ...


3

Foreword I've been tuning HAProxy for a while and done a lot of performance testing on it. From 100 HTTP requests/s to 50 000 HTTP requests/s. The first advice is to enable the statistics page on HAProxy. You NEED monitoring, no exception. You will also need fine tuning if you intend to go past 10 000 requests/s. Timeouts are a confusing beast because ...


1

You misunderstand the "lack" of SNI support. First, nginx is generally fine for "wildcard" SSL setups. The support issue is in older clients (i.e. browsers), which are not capable of handling SNI.


0

Yeah, it's possible. Stick tables enable a client-server persistance, but they don't define which server a given client ends up on. That's what the cookie directive does (in combination with the cookie option to the server directives). Unfortunately, if your client doesn't support cookies, it's not of much use. The way to get around that is by having a ...


0

StartSSL splits their certificate distributions into sub-packages for use with the common server setups - IIS, Apache and Nginx - each simply contains the common naming scheme and appropriate intermediate certificate bundling. The package OtherServer.zip has the individual certificates separated as individual files: the intermediate, your issued cert, and a ...


0

the logging via unix socket log does not work for me on my rhel 6.7.you can have a try with this conf. haproxy (working on 81) forward http request to httpd (working on 80) /etc/haproxy/haproxy.cfg frontend web_front log 127.0.0.1 local6 option httplog bind *:81 default_backend web_back backend web_back server ...


1

There are numerous asynchronous DNS fixes in HAProxy after 1.6.1 but prior to the release of version 1.6.5, which is the current release as of this writing. I wasn't able to pinpoint a single fix in the changelog that obviously explains exactly the condition you encountered, but if I remember correctly, name resolution at startup is done synchronously, ...


0

You're using option http-server-close. SCL: server close ("option http-server-close") : the server-facing connection is closed after the end of the response is received, but the client-facing connection remains open. http://cbonte.github.io/haproxy-dconv/configuration-1.6.html#4 The front-end connections are browser connections that have ...


0

There are a number of issues. The file /usr/share/nginx/html/nginx.conf is the contents of a server block and is not currently complete enough to do anything useful. I would suggest that /etc/nginx/sites-enabled/default contains the server block that is currently running your site. Look at this document for more on server blocks. The location / block ...


0

If you have sure that your configurations files is right, make the file yourself, but make sure to give permissions to syslog user. chown syslog:adm /var/log/haproxy.log This should do the trick. Make sure to restart both rsyslog and haproxy.


0

While max_allowed_packet does usually work in most cases. This problem is actually a bug in the Zabbix database connection. So to answer the question you have to patch or use Zabbix version 2.5.0 or above. source: https://support.zabbix.com/browse/ZBX-6163


0

Please restart haproxy to create new file. For erasing haproxy use this command Echo > /haproxy log location



Top 50 recent answers are included