Hi @alex.contis_1,
The output for curl -I -v $SERVICE_URL seems fine. What happens when you add -L?
from the curl man page:
-L (HTTP/HTTPS) If the server reports that the requested page has moved to a different location (indicated with a Location: header and a 3XX response code), this option will make curl redo the request on the new place.
So that would make curl follow up and request https://kaltura.myserver.bla/start/index.php, this should return http 200.
Also, is the settings.serviceUrl in /opt/kaltura/app/configurations/admin.ini set correctly?
What about serviceUrl in /opt/kaltura/app/configurations/batch/batch.ini?
Also make sure the secret directive is set correctly and matches the value of:
# mysql -h$DB1_HOST -u $DB1_USER -p$DB1_PASS -P$DB1_PORT $DB1_NAME
mysql> select admin_secret from partner where id=-1;
Assuming everything is set correctly, run:
# curl -f "$SERVICE_URL/api_v3/index.php?service=system&action=ping"
A correct response should be:
HTTP/1.1 200 OK
and an XML similar to the below:
<?xml version="1.0" encoding="utf-8"?><xml><result>1</result><executionTime>0.033658981323242</executionTime></xml>
After confirming all of the above, try to log into the Admin Console while looking at the log here:
/opt/kaltura/log/kaltura_admin.log
and the API log here: /opt/kaltura/log/kaltura_api_v3.log
look for erroneous patterns with grep like so:
grep -A 1 -B 1 --color "ERR:\|PHP\|trace\|CRIT\|\[error\]"
and then run through the lines leading to the final error to understand what went wrong.