Hello Errick, Probably a wrong certificate format.
You can check the haproxy log to see the exact issue. journalctl -u packetfence-haproxy-portal Thanks, Ludovic Zammit Product Support Engineer Principal Lead Cell: +1.613.670.8432 Akamai Technologies - Inverse 145 Broadway Cambridge, MA 02142 Connect with Us: <https://community.akamai.com/> <http://blogs.akamai.com/> <https://twitter.com/akamai> <http://www.facebook.com/AkamaiTechnologies> <http://www.linkedin.com/company/akamai-technologies> <http://www.youtube.com/user/akamaitechnologies?feature=results_main> > On Mar 1, 2024, at 7:14 PM, Errick via PacketFence-users > <packetfence-users@lists.sourceforge.net> wrote: > > Hi All, > > Have a single server running Packetfence and using Lets Encrypt certificates > via manual renewal. After applying the new certs (server.crt, server.key, > server.pem) from the LetsEncrypt .pem and .key files, we are seeing > haproxy-admin fail to start with exit code 1. > > It is unable to start manually or via pfcmd service pf start. > > Rolling back to the old certs immediately resolves the issues and > haproxy-admin can start successfully. > > I do not see any error information in systemctl status nor in journalctl -xe > for this service when it fails. > > Any ideas on ways to troubleshoot or fix this? > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://urldefense.com/v3/__https://lists.sourceforge.net/lists/listinfo/packetfence-users__;!!GjvTz_vk!Ql7-VgWeCuwSZ_NNLguh8MN2gK2ieGRHSiH5MEU7Que_pNLV_gHwl1fOeUgcd5gM_ZEkmC1imJE9dx2mZG6bv0nahrCfbZUgFjh9jA$ >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
