General settings
Use General settings to configure the Engine hostname and HTTPS certificate, synchronize time, change instance-wide options, and back up or restore configuration.
Choose this whenYou are changing instance-wide hostname, TLS, time, backup, or restore settings—not a media workflow.
Use another module whenUse the owning media module for a single stream, player, recording, route, or room.
/api/application/getAppInfoBefore you start
getAppInfo is a public read method. Configuration, certificate, export, and import operations require a valid x-access-token. Use an account with administrative responsibility for the instance and back up current settings before changing connectivity or importing a database.
What you can do
getAppInforeads application and instance information.updateHttpConfigchanges HTTP and hostname settings.updateSslCertificateinstalls or replaces TLS material.updateCustomSettingschanges supported instance options.updateNtpConfigurationconfigures time synchronization.exportDbandimportDbsupport configuration backup and restore.
Example workflow
- Read application information and export the current database.
- Update the hostname and HTTP configuration.
- Install the matching TLS certificate.
- Verify the dashboard and API on the final HTTPS address.
Common use cases
- Move an Engine instance from an IP address to a production hostname.
- Rotate an expiring TLS certificate without rebuilding media workflows.
- Back up configuration before an upgrade or infrastructure change.
Limits and troubleshooting
An incorrect hostname, certificate, or HTTP configuration can make the instance unreachable. Database import can replace existing configuration, so validate the backup and maintenance window first. Keep system time synchronized because certificates, tokens, and distributed workflows depend on it.
Next steps
After connectivity is stable, configure Ports, Cluster nodes, or the ingest module needed by the workflow.
Configure the Engine HTTP and TLS boundary
Read the current application settings, choose the required HTTP mode, and install the certificate used by API and media-facing services.
- Read current settingsCapture the current mode and application state before changing the listener.
POST /api/application/getAppInfo - Set the HTTP modeApply the reviewed HTTP or HTTPS listener configuration.
POST /api/application/updateHTTPConfig - Install the certificateUpdate the certificate material only after its names and chain are verified.
POST /api/application/updateSSLCertificate
Changing HTTP or certificates can interrupt active clients. Validate DNS, certificate chain, ports, and rollback access before applying it.
Use this public bootstrap call to inspect Callaba Engine application details before making instance-wide changes. No API token is required.
The response includes node_app, stack_version_name, stack_version, custom_settings, http_modes, needLicenceKey, conference URLs under global_module_settings, and read_preference.
The success field is spelled suceess. Clients must read that exact response field.
Current deployment flavor and stack version fields read from the application record and environment.
Current HTTP delivery modes stored on the application record.
Persisted custom application settings.
Indicates whether the application record currently has no licence key.
Current wss_server_url and turn_server_url values for conference connectivity.
Resolved database read preference; the backend falls back to its primary-read constant.
The live backend currently returns this misspelled field with value true.