I`m trying to reconfigure Kaltura instance for external access via domain.
Everything is ok without the playing. I configured kaltura for “kaltura.local” domain via kaltura-config-all.sh, but KMC still uses ‘localhost’ urls for streaming.
Hello,
I have next question. I configured it as You suggested but still have problem with KMC urls.
After Publisher “Manage” action clicked Kaltura still redirects me to ‘localhost’ domain.
This is taken from /opt/kaltura/app/configurations/admin.ini
the settings.serviceUrl directive.
I believe you did not rerun the config scripts as explained in the page I linked to, however, otherwise, it would have changed.
Nonetheless, you can change it manually and reload your apache. However, there are multiple places to change which is why rerunning the config scripts is a better option.
It is recommended that you do work using HTTPs. Would you like to continue anyway?[N/y]
Which port will this Vhost listen on? [80]
Please select one of the following options [0]:
So there is no way to configure hosts…
And when I running kaltura-config-all.sh after providing api host, nginx host and port I have error:
Nginx port to listen on [88]:
Reloading nginx: [ OK ]
Running DWH config...
kaltura-dwh-9.4.0-2.noarch
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:
# rm /opt/kaltura/app/base-config.lock
# /opt/kaltura/bin/kaltura-base-config.sh
ERROR: /opt/kaltura/bin/kaltura-dwh-config.sh failed:( You can re-run it when the issue is fixed.
====================================================================================================================
Setup completed successfully!
To access your Kaltura tools visit:
http://localhost:80
To change the hostname, running front-config is not enough.
If you are using an all in 1 instance, run kaltura-config-all.sh and provide the new hostname and service URL whenever prompted.
You don’t need to rerun kaltura-dwh-config.sh since that one does not need the service URL and has no UI facing implications.