Hi Fabrice,
Just to provide feedback:
On 21-6-2017 1:10, Durand fabrice via PacketFence-users wrote:
I just tried upgrading our production network from 5.6 to 7.1, and
even though things seemed to have worked out, after a while we
discovered that some nodes were 'unregistered' after the upgrade.
(they were registrered before the upgrade, on 5.6.1)
Also, unlike normally, these unregistered nodes were not directed to
the captive portal, but they received a firefox timeout error. (pf
dhcp had given them sane looking ip/gateway/dns)
does the dns answer ?
what about netstat -nlp| grep 80
The problem turned out to be: haproxy not starting, due to a corrupted
server.pem. (I stupidly pasted something wrong...)
Thanks for your help!
And this might help others: In the case of Let's Encrypt certificates,
the haproxy cert.pem has to contain:
* server.company.com.cer
* server.company.com.key
and *ALSO*
* fullchain.cer
Otherwise various browsers will complain about the certificate.
Everything running nicely now. :-)
MJ
------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
