Hi Guys,

We have a number of PF sites ranging from old CentOS 7 based installations
to debian 11.11 using PF 11.2. Issue has only started recently.

The following errors appear in the *haproxy_portal.log*

May 20 10:15:42 site haproxy[1233398]: 192.168.96.199:64611
[20/May/2025:10:15:42.743] portal-https-66.70.255.147/1: SSL handshake
failure
May 20 10:15:42 site haproxy[1233398]: 192.168.96.199:64613
[20/May/2025:10:15:42.743] portal-https-66.70.255.147/1: SSL handshake
failure
May 20 10:15:42 site haproxy[1233398]: 192.168.96.199:64612
[20/May/2025:10:15:42.743] portal-https-66.70.255.147/1: SSL handshake
failure

It causes users to experience a message on their device showing:

*This connection is not private. This website maybe impersonating
packetfence.packetfence.org <http://packetfence.packetfence.org> to steal
your personal information.*


We use our own DigiCert certificate for our own domain and have PF
configured appropriately.

The IP address showing up is: 66.70.255.147
That resolves to: 147.255.70.66.in-addr.arpa domain name pointer
setup.mts.ca.
Entering a lookup gives this: Host setup.mts.ca not found: 3(NXDOMAIN)

The IP address above is used under Advanced Access Configuration > Portal >
IP Address.

The question here is that the IP no longer resolves when entering "host
setup.mts.ca" - would that cause the issue and how to fix i.e., what
alternative IP address to use? Still not sure if the error reported by
users would be caused by this issue.

Any suggestions would be welcome.

Tony
_______________________________________________
PacketFence-users mailing list
PacketFence-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to