[x] This is not a support request or question that should be posted on the Kaltura forum
Bug report
*Please provide steps to reproduce, including errors from /opt/kaltura/log/kaltura_api_v3.log, /opt/kaltura/log/kaltura_apache_errorslog and /opt/kaltura/log/kaltura_prod.log:**
Basically, what web browser sees is Host: whateverhostname:NN when api calls are used. This is OK for internal network traffic in plain http, but a modern browser does not fear well with a protocol and port mismatch ( it is truing to do http over port 80 ) and it interprets the error as a CORS issue.
Altering the request manually in the browser and changing the 80 for a 443 leads to a 200 code( although the process does not change).
This all works fine if https is dropped and plain http is used. So it is entirely an issue of protocol and port mismatch.
Possible solution ( although I am not sure): make sure that the application does not attach the port to the Host portion of the request.
Maybe that is useful in some scenarios, but it currently breaks KMC login over https.
Bug report
*Please provide steps to reproduce, including errors from /opt/kaltura/log/kaltura_api_v3.log, /opt/kaltura/log/kaltura_apache_errorslog and /opt/kaltura/log/kaltura_prod.log:**
Issue explain in detail here: https://forum.kaltura.org/t/distributed-kaltura-ce-installation-works-but-cant-log-in-lots-of-questions/10960/2
You see a request like this being generated:
Basically, what web browser sees is Host: whateverhostname:NN when api calls are used. This is OK for internal network traffic in plain http, but a modern browser does not fear well with a protocol and port mismatch ( it is truing to do http over port 80 ) and it interprets the error as a CORS issue.
Altering the request manually in the browser and changing the 80 for a 443 leads to a 200 code( although the process does not change).
This all works fine if https is dropped and plain http is used. So it is entirely an issue of protocol and port mismatch.
Possible solution ( although I am not sure): make sure that the application does not attach the port to the Host portion of the request.
Maybe that is useful in some scenarios, but it currently breaks KMC login over https.
Linux distribution name and version:
CentOS Linux release 7.9.2009 (Core)
Are you using the RPM or deb packages?
When using RPM, paste the output for:
For deb based systems:
Is this an all in one instance [single server] or a cluster?
If applicable, please provide the MySQL version
mysql Ver 15.1 Distrib 5.5.68-MariaDB, for Linux (x86_64) using readline 5.1
If you're having an issue with a specific media asset, please provide a link from which it can be downloaded/played: