Hi
tcp 0 0 1.1.1.1:443 0.0.0.0:*
LISTEN 1860/httpd
tcp 0 0 1.1.1.1:80 0.0.0.0:*
LISTEN 1860/httpd
tcp 0 0 1.1.1.3:443 0.0.0.0:*
LISTEN 1697/haproxy
tcp 0 0 1.1.1.3:80 0.0.0.0:*
LISTEN 1697/haproxy
tcp 0 0 1.1.2.1:443 0.0.0.0:*
LISTEN 1860/httpd
tcp 0 0 1.1.2.1:80 0.0.0.0:*
LISTEN 1860/httpd
tcp 0 0 1.1.2.3:443 0.0.0.0:*
LISTEN 1697/haproxy
tcp 0 0 1.1.2.3:80 0.0.0.0:*
LISTEN 1697/haproxy
tcp 0 0 192.168.149.218:1443 0.0.0.0:*
LISTEN 1690/httpd
tcp 0 0 192.168.149.220:1443 0.0.0.0:*
LISTEN 1690/httpd
tcp 0 0 192.168.149.220:443 0.0.0.0:*
LISTEN 1697/haproxy
tcp 0 0 192.168.149.220:80 0.0.0.0:*
LISTEN 1697/haproxy
My management address is 192.168.149.218 on this node, with a vip of .220. I
can manage the node(s) locally on their physical addresses with...
https://192.168.149.218:1443/
https://192.168.149.219:1443/
...but management on https://192.168.149.220:1443/ does not work. And it's not
a surprise... the haproxy turns out to listen on 443. Checking the config
file...
[root@mcjs-pfence3a lgjh]# tail -20 /usr/local/pf/var/conf/haproxy.conf
frontend portal-http-mgmt
bind 192.168.149.220:80
reqadd X-Forwarded-Proto:\ http
default_backend portal-mgmt-backend
frontend portal-https-mgmt
bind 192.168.149.220:443 ssl no-sslv3 crt
/usr/local/pf/conf/ssl/server.pem
reqadd X-Forwarded-Proto:\ https
default_backend portal-mgmt-backend
backend portal-mgmt-backend
balance source
option httpclose
option forwardfor
server 192.168.149.218 192.168.149.218:80 check
server 192.168.149.219 192.168.149.219:80 check
Lo... the mgmt proxy sends to 192.168.149.218 ... but nothing is listening on
that. What's up with that?
Thanks for any help!
Greg
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users
