media server logo
دليل استخدام المنتج

الإعدادات العامة والوصول والشهادات

Manage the administrator profile, API token, public domains, time, WebRTC infrastructure, HTTPS certificates, licence and configuration backups.

مكانه في CallabaAdvanced → General settings
ما الذي تفعله هذه الوحدة

These settings define how people, APIs and browsers reach the instance. Change one section at a time so a domain, certificate or time change cannot hide the real cause of a connection failure.

قبل البدء

  • Administrator access to the Callaba instance.

  • DNS control for every hostname you plan to use.

  • A copy of the current configuration before changing domains, certificates or importing a backup.

شرح الإعدادات

نشرح عناصر التحكم التي يحتاجها المشغّل فقط، ولا نعرض أسماء الحقول الداخلية أو أحداث التنفيذ.

Account and API access

Identity and automation credentials for this instance.

Administrator name and email

The operator identity shown by the dashboard.

Password

Reset the dashboard password from the authenticated account.

Use a unique password and store it outside the browser.
API token

Copy the dashboard-issued token used by authenticated Engine API requests.

Treat it as a secret; rotate access if it is exposed.

Public addressing

Hostnames used by media delivery and browser access.

CDN domain

Optional public domain used when media is delivered through your CDN or load balancer.

Streaming domain

Hostname Callaba places into generated playback and connection URLs.

Point DNS to the instance or the intended fronting service before changing it.

Time and browser communication

Infrastructure used by scheduled events and WebRTC rooms.

NTP server

Time source for synchronized certificates, logs, scheduled playback and distributed operations.

TURN server URL

Relay endpoint used when WebRTC participants cannot connect directly.

WebSocket server URL

Secure signalling endpoint used by video-call browser clients.

HTTPS certificate

Choose one certificate mode and provide only the fields required by that mode.

Automatic certificate

Request and renew a public certificate for a DNS name that resolves to this instance.

Confirm ports and DNS reachability before requesting it.
Self-signed certificate

Create an encrypted local certificate for controlled testing.

Browsers will not trust it publicly without a private trust policy.
Custom certificate

Install your own certificate and matching private key.

Paste the complete certificate chain and verify the key matches before saving.
Certificate domain

The hostname covered by the selected certificate.

Self-hosted lifecycle

Settings used to recover or move an installation.

Licence key

Activate a self-hosted Callaba licence on the instance.

Import configuration

Restore a compatible Callaba configuration archive.

Import only into the intended instance and keep the pre-import backup.
Export configuration

Download selected module configuration as a recovery artifact.

Store exports away from the instance they protect.

أول مسار آمن

  1. 01

    Update the account identity and copy the API token only if an integration needs it.

  2. 02

    Set the streaming hostname after DNS resolves to the intended instance or load balancer.

  3. 03

    Choose automatic, self-signed or custom HTTPS and complete only that certificate path.

  4. 04

    Set NTP and, for video calls, the TURN and secure WebSocket endpoints.

  5. 05

    Open the dashboard in a new private browser session before closing the current session.

  6. 06

    Export the resulting configuration and keep the file outside this server.

أمثلة لمسارات العمل

استخدمه عندما

Publish the dashboard with an automatic HTTPS certificate

A self-hosted instance has a public DNS name and should be trusted by browsers.

DNSHostname resolves
General settingsDomain + automatic TLS
CertificateIssued and active
BrowserTrusted HTTPS
مخطط متحرك لمسار العمل: Publish the dashboard with an automatic HTTPS certificate

كيفية بنائه

  1. 1

    Point the chosen hostname to the public entry point and wait until DNS resolves externally.

  2. 2

    Set the streaming domain and select the automatic certificate option.

  3. 3

    Enter the certificate domain, save, and wait for the certificate details to appear.

  4. 4

    Open the HTTPS URL in a private browser session and inspect the certificate hostname and expiry.

استخدمه عندما

Move configuration to a recovery instance

You need a controlled backup before maintenance or a planned rebuild.

Running instanceSelect modules
ExportEncrypted handling
Recovery instanceImport
ValidationOne live path
مخطط متحرك لمسار العمل: Move configuration to a recovery instance

كيفية بنائه

  1. 1

    Export the required module configuration and record the source application version.

  2. 2

    Create a separate recovery instance with compatible software and network prerequisites.

  3. 3

    Import the archive once; do not mix it with unrelated manual changes.

  4. 4

    Verify account access, domains, one input and one output before declaring recovery ready.

تحقق من النتيجة

  • A private browser session can sign in through the intended HTTPS hostname.
  • The certificate covers the hostname and shows the expected expiry.
  • NTP-backed time is correct in logs and scheduled browser events.
  • The exported configuration can be downloaded and stored outside the instance.

استكشاف الأخطاء

Automatic certificate issuance fails

تحقق
  • Resolve the certificate domain publicly.
  • Check the fronting firewall/load balancer and challenge path.
ثم نفّذ

Correct DNS and reachability, then request the certificate again; do not switch certificate modes repeatedly.

The dashboard is unreachable after a domain change

تحقق
  • Try the previous hostname in the still-open session.
  • Confirm the new DNS target and certificate hostname.
ثم نفّذ

Restore the last known domain from the active session or server console before changing any other setting.

Video-call browsers cannot connect

تحقق
  • Confirm the secure WebSocket URL.
  • Test TURN reachability from the affected network.
ثم نفّذ

Correct signalling first, then test TURN relay separately with one browser pair.