Domain change/HTTPS migration

If you move your Opencast server to a new domain or if you switch from HTTP to HTTPS, you will change org.opencastproject.server.url in etc/ But if your Opencast already processed events, these events still contain the old URL in various places. So in order for old events to work correctly, you have to migrate them. Re-processing or re-publishing will update the links but this may not be an option if you have many events. In that case, the following steps might help.

Note that you modify stored data directly without any safety nets usually provided by Opencast. You should understand what you are doing!

  1. Backup your database and the OpenSearch/Elasticsearch indices (in {data}/index)!
  2. Change org.opencastproject.server.url and test your set-up with a new publication (i.e. uploading a video).
  3. Put all your nodes into maintenance mode or, at least, do not process any videos.
  4. Update the media packages on disk. Run the following in the folder configured in (usually your NFS). Note: only the subfolders archive/ and downloads/ will be affected by this, so you can also run it in those two individually. This is especially useful to reduce the execution time of the command if your NFS contains other, Opencast-unrelated files (e.g. .snapshots/).

     # This changes the domain AND from http to https. Carefully adjust the command as needed!
     # Your old URL may or may not have the port explicitly listed.  Check the previous value of org.opencastproject.server.url and match that.
     find . -type f -name "*.xml" -exec \
        sed -i 's#' {} +
  5. Update database tables. Note: there more than the following two tables containing the old domain name, but only these two are relevant.

     -- Reminder: Your old domain name may or may not have its port listed.  Use old value for org.opencastproject.server.url here.
     UPDATE oc_assets_snapshot SET mediapackage_xml = REPLACE(
        mediapackage_xml, '', '');
     UPDATE oc_search SET mediapackage_xml = REPLACE(
        mediapackage_xml, '', '');
  6. Rebuild the OpenSearch/Elasticsearch indices using the REST endpoint listed in the docs: