Dear HAProxy Community,
We are seeking your guidance with regard to the following issue we are facing with our HAProxy use. ------ ISSUE ------- When we use a single monolithic config file (haproxy.cfg), HAPRoxy launches fine and we are able to access our products that use HTTP/TCP (WebSockets) and RTMP. When we launch HAProxy using multiple config files in a directory, HAProxy launches fine. However, our products do not allow administrator to login (i.e., locks out). We have to reset the password to login. Once the admin logs out, again it locks out the administrator and the password has to be reset to login. How is using multiple HAProxy config files in a directory connected to logging in to our WebSocket product? ---- DETAILS ---- We are running HAProxy as a daemon service. We are using HAProxy init script from HAProxy's Github source. /etc/init.d/haproxy has the following lines: Option 1: When using SINGLE Config FILE CFG=haproxy-1.7.5/conf/$BASENAME.cfg Option 2: When using a config DIRECTORY (conf.modular) with multiple files in alphanumerical order, namely global, defaults, frontend, backend, dns resolver and statistics: CFG=haproxy-1.7.5/conf.modular Environment: HAProxy version: 1.7.5 CentOS 7.2 Lua 5.3 Zlib compression PCRE 8.3x OpenSSL 1.0.2k Thank you. Sincerely, Hemant K. Sabat Coscend Communications Solutions Web site: <http://www.coscend.com/> www.Coscend.com ------------------------------------------------------------------ Real-time, Interactive Video Collaboration, Tele-healthcare, Tele-education, Telepresence Services, on the fly. ------------------------------------------------------------------ CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail Messages from Coscend Communications Solutions' posted at: <http://www.coscend.com/Terms_and_Conditions.html> http://www.Coscend.com/Terms_and_Conditions.html
