0
Do we have to disable Apache's ssl mode using the command a2dismod ssl for using the mentioned setup as while starting haproxy, it is complaining about port 443 is already being used?
Rajat Saxena
Posted 2017-02-09T03:47:19.540
Reputation: 129
1
If I have understood correctly, then you have a server that runs apache and haproxy. And now apache reports the already being used error? So this means that both try to use the 433 port.
So yes, you can (and need to) disable the ssl module and/or deactivate the listen XXX:443 configuration line.
Lutz Reinhardt
Posted 2017-02-09T03:47:19.540
Reputation: 81
This, or move apache https port to something else (444?), in your ports.conf and virtualhosts. Make sure haproxy adds the X-Forwarded-Proto header/could be required by your balanced app. – SYN – 2017-02-19T12:08:01.910
Why would you run both apache and haproxy on the same server? Do you need to balance inbound connections to a single/local-hosted backend?! – SYN – 2017-02-19T12:05:56.400