Hello Community
Finally, I managed to move my HTTP checkMK to HTTPS. Now it’s so secure as I can not log in anymore 
I have integrated LDAP to checkMK but after my change to HTTPS, I’m not able to log in anymore.
The check of the apache log files ( ssl_access_log and ssl_request_log ) shows the following
ssl_request_log
[08/Nov/2022:16:13:00 +0100] XXX.XXX.XXX.XXX TLSv1.3 TLS_AES_256_GCM_SHA384 “-” -
[08/Nov/2022:16:13:56 +0100] XXX.XXX.XXX.XXXTLSv1.3 TLS_AES_256_GCM_SHA384 “POST /main/check_mk/login.py HTTP/1.1” 1928
[08/Nov/2022:16:13:57 +0100] XXX.XXX.XXX.XXXTLSv1.3 TLS_AES_256_GCM_SHA384 “POST /main/check_mk/login.py HTTP/1.1” 1928
[08/Nov/2022:16:14:18 +0100] XXX.XXX.XXX.XXXTLSv1.3 TLS_AES_256_GCM_SHA384 “-” -
ssl_access_log
XXX.XXX.XXX.XXX - - [08/Nov/2022:16:15:10 +0100] “POST /main/check_mk/login.py HTTP/1.1” 200 1928
XXX.XXX.XXX.XXX - - [08/Nov/2022:16:15:11 +0100] “POST /main/check_mk/login.py HTTP/1.1” 200 1928
XXX.XXX.XXX.XXX - - [08/Nov/2022:16:15:31 +0100] “-” 408 -
On the LDAP settings in checkMK, if I test my bevor worked settings I get the following messages:
ldaps://DC_Domainname.com:636: {‘result’: -1, ‘desc’: “Can’t contact LDAP server”, ‘ctrls’: [], ‘info’: ‘error:1416F086:SSL routines:tls_process_server_certificate:certificate verify failed (unable to get local issuer certificate)’}
Does anyone know what I have to check to solve this issue?
thanks for your help
Roberto