Reverse Proxy
An Enterprise deployment can expose QSDA through a reverse proxy, including under a URL prefix such as https://qsda.example.com/qsda.
- Set Control Panel > Configuration > Service Parameters > UI Base Path to
/qsda. - Configure the proxy to forward the request path, including
/qsda, to the QSDA UI port (default 5003). Preserve the path prefix; QSDA uses it as its application base path. - Configure the proxy to support WebSocket connections for the Blazor UI and notifications.
- Restart QSDA after changing its base path. Test the browser UI, Qlik login callbacks, downloads, and API documentation through the public address.
Use the public scheme, host, port, and prefix consistently. For example:
Browser: https://qsda.example.com/qsda
API documentation: https://qsda.example.com/qsda/api-docs
CLI: qsda-cli connections list --server https://qsda.example.com/qsda
Configure Qlik OAuth/web-integration origins for the public address used by the browser. A base path is part of the application URL, not an origin; origin configuration uses the scheme, host, and port. Retest authentication after proxy changes.
Forward public requests to the UI, rather than exposing the loopback API service on port 5000. See Service Parameters.