KMC login failed KMC.mxml, KMC uiconf load failed: Error 2032

I think I already found the answer in local.ini file for KMC login failed.

https://mydomain.ca:80/api_v3/index.php?service=multirequest&action=null&kalsig=45d90b37a2cf51d9a233e88a1e7bc9ed

Kaltura port 80
Proxy port 443

This site can’t provide a secure connection
mydomain.ca sent an invalid response.
Try running Windows Network Diagnostics.
ERR_SSL_PROTOCOL_ERROR

https://mydomain.ca/index.php/kmc/kmc4

apachectl -S
VirtualHost configuration:
wildcard NameVirtualHosts and default servers:
*:80 mydomain.ca (/etc/httpd/conf.d/zzzkaltura.conf:1)
Syntax OK

cat /etc/httpd/conf.d/zzzkaltura.conf
<VirtualHost *:80>
ErrorLog “/opt/kaltura/log/kaltura_apache_errors.log”
CustomLog /opt/kaltura/log/kaltura_apache_access.log vhost_kalt

    Include "/opt/kaltura/app/configurations/apache/conf.d/enabled.*.conf"

I just have found in local.ini

CDN URLs
cdn_api_host = mydomain.ca:80
cdn_api_host_https = mydomain.ca:80
stats_host = mydomain.ca:80
stats_host_https = mydomain.ca:80

and it should be

CDN URLs
cdn_api_host = mydomain.ca
cdn_api_host_https = mydomain.ca
stats_host = mydomain.ca
stats_host_https = mydomain.ca

±----±-----------------------------------------±-------------------------------±-----------------------+
| id | name | url | host_name |
±----±-----------------------------------------±-------------------------------±-----------------------+
| 1 | Default HD Network Live Delivery Profile | NULL | NULL |
| 2 | Default HDS Live Delivery Profile | NULL | NULL |
| 101 | Default HLS Live Delivery Profile | NULL | NULL |
| 201 | Default RTMP Live Delivery Profile | NULL | NULL |
| 500 | Default HTTP Delivery Profile | https://mydomain.ca |mydomain.ca |
| 501 | Default HTTP Delivery Profile | https://mydomain.ca | mydomain.ca |
±----±-----------------------------------------±-------------------------------±-----------------------+

The error message ERR_SSL_PROTOCOL_ERROR error indicates that the browser is not able to initiate the secured communication at the moment. It’s almost impossible to pin it down to a single cause, it could be almost anything. There is no definite guide for managing this error. However, there are few changes or settings which help you to get rid you of this error.

Configure Correct Date and Time
Clear Browsing Data
Clear Your SSL State
Disable QUIC Protocol of Chrome
Disable your Internet Browser Extensions
Adjust Your Internet Security and Privacy Level
Remove your system hosts file
Check Your Antivirus Settings
Check Your Firewall