Application gateway and domains

Before configuring a domain, identify the public gateway for this installation and arrange DNS and TLS access with its operator. Use the same external address when configuring the backend's public endpoints and provider callbacks.

Assign each hostname a role

The managed application and API use app.intracord.hu; the marketing website uses intracord.hu; standalone documentation uses docs.intracord.hu. A bundled installation can serve documentation under the application host's /docs path. Your own installation can use different hostnames with the same roles.

Route the application traffic

Forward /api/v1/ and /api/v2/ to the backend. The UI's /api/auth/ and /api/config/ routes must still reach the UI. Preserve WebSocket upgrades and the external scheme and host so signed phone callbacks are validated against the public URL. The supplied gateway templates include these routes.

TURN uses separately exposed media ports and its own reachable hostname. HTTPS access to the application does not establish that the TURN relay is reachable. Follow the ports specified by the deployment template you use.

Verify through the public address

Check login, the documentation language selector, a v2 authenticated read and a browser voice call. Then verify the carrier callback with a controlled phone call. Repeat these checks after changing a hostname or proxy, because an internal health check does not exercise the public path.