Product knowledge
Docs
Troubleshooting
Find out whether a problem comes from installation, HTTPS, identity, Qlik access or a specific feature.
On this page
Setup does not complete
Use Open installation log in Setup and record the phase and message. The current Windows installer checks local administrator rights, 64-bit Windows, free space, the chosen account, installation paths and required ports before it starts. Resolve the reported prerequisite rather than repeatedly starting another installation.
Use Full Setup when Updater reports a missing prerequisite, a required PostgreSQL configuration transfer or an interrupted installation. If Setup offers Recover Raptor, finish recovery first. Keep the existing configuration, database, repository and operation records until recovery is verified.
Get-Service -Name raptor-mcp-gateway, raptor-postgresqlThe Gateway address does not open
Check the configured hostname, DNS result and port from the affected client computer. A fresh Windows installation uses https://<gateway-hostname>:7443/hub. The loopback listener on 7331 is for the local machine; it is not the browser address to distribute to other users.
A working health response confirms that the listener answers. It does not prove licence activation, user sign-in, tool permissions or access to a Qlik app. Check those independently after restoring connectivity.
Invoke-RestMethod -Uri 'https://gateway.example.com:7443/healthz'The browser or client reports a certificate error
Use the canonical hostname covered by the Gateway certificate. Setup installs trust on its own Windows computer; another browser or MCP client may still need your organization to distribute the issuing root. Some clients use a separate trust store.
For an imported certificate, check its validity, chain and subject alternative names against every configured browser address. Keep the existing certificate settings through updates. If maintenance cannot read the active certificate settings, stop and review the installation log rather than replacing the certificate files by hand.
The licence or available tools are wrong
Review the activated licence, assigned seat, Raptor role and Qlik identity. A client connection can succeed while the user has no permitted tools. Confirm that the client uses that user’s own Gateway token and the correct Gateway endpoint.
After activation, the encrypted licence record is authoritative. Editing the old licence value in .env and restarting or running Updater does not replace it. Use the Gateway activation form or the installed licence command to validate and deliberately replace the key.
.\scripts\license.ps1 -StatusQlik sign-in or app access fails
For Qlik Sense on Windows, check the configured Qlik server address and Qlik browser address separately. The server address must match the certificate-backed QRS endpoint. The browser address can include a virtual proxy prefix and must be the address users actually use, without /hub or query parameters.
Changing the browser address invalidates an activated Windows sign-in bridge. Download a fresh bridge package and follow the supported removal and reinstall procedure before activating it again. Do not delete a shared certificate or change Qlik bindings to repair the Gateway.
For either Qlik platform, verify that the user can open the intended app in Qlik and has the required permission there. Gateway roles do not grant Qlik app access.
Collect useful support evidence
For a feature-specific failure, record the operation, time, affected user, app or task ID, and any returned error or receipt. Check its connection, licence and role requirements before changing configuration. A running database alone does not establish that writeback, repository or workflow operations are ready.
Include the Gateway version, installation or update log, browser/client name and the steps that reproduce the issue. Windows fresh-install operation records are under %ProgramData%\RaptorGatewaySetup\operations. Older-installation migration records use the migrations folder alongside it. Review evidence before sharing; exclude passwords, licence keys, bearer tokens and private certificates.
Related guides
Previous
Updates and maintenance
Next