https://community.checkpoint.com/t5/SASE-and-Remote-Access/Certificate-is-badly-signed/m-p/188435#M4675 <P>Please open a TAC case for this: <A href="https://help.checkpoint.com" target="_blank">https://help.checkpoint.com</A></P> Wed, 02 Aug 2023 12:56:29 GMT _Val_ 2023-08-02T12:56:29Z https://community.checkpoint.com/t5/SASE-and-Remote-Access/Certificate-is-badly-signed/m-p/188056#M4674 <P>So we made a mass upgrade from 81.20 to 87.20 to almost all our clients</P><P>&nbsp;</P><P>But then suddenly more then 10-15 user have "Certificate is badly signed".</P><P>&nbsp;</P><P>Our only solution is to downgrade to 81.20</P><P>&nbsp;</P><P>But we want to avoid it.</P><P>&nbsp;</P><P>We know it is know a certificate problem, because it works on older versions and in different computers. But a lot of computer still throws "Certificate is badly signed"</P><P>&nbsp;</P><P>Is there someone who can shed some light ?</P> Mon, 31 Jul 2023 06:50:13 GMT https://community.checkpoint.com/t5/SASE-and-Remote-Access/Certificate-is-badly-signed/m-p/188056#M4674 Remchuk 2023-07-31T06:50:13Z https://community.checkpoint.com/t5/SASE-and-Remote-Access/Certificate-is-badly-signed/m-p/188435#M4675 <P>Please open a TAC case for this: <A href="https://help.checkpoint.com" target="_blank">https://help.checkpoint.com</A></P> Wed, 02 Aug 2023 12:56:29 GMT https://community.checkpoint.com/t5/SASE-and-Remote-Access/Certificate-is-badly-signed/m-p/188435#M4675 _Val_ 2023-08-02T12:56:29Z