Skip to main content
Version: V3.8

Service Parameters

Use the Control Panel's Configuration dialog to configure the QSDA services. Save changes and restart the services when the Control Panel indicates a restart is required.

Addresses and timeouts​

UI Port is the browser, CLI, and external API port. The default is 5003. With an Enterprise license, the UI can listen for remote connections; otherwise it is limited to localhost.

API Port defaults to 5000 and is loopback-only. It connects the UI to the API service. External scripts should use the UI address, which proxies API requests internally.

HttpClient Timeout defaults to 100 seconds. Increase it if outbound HTTP requests exceed that limit.

UI Base Path is an optional URL prefix, such as /qsda, when a reverse proxy serves QSDA under a subpath. Include it in browser, CLI, and API addresses: for example https://qsda.example.com/qsda/api-docs. See Reverse Proxy.

Use HTTPS requires an Enterprise license and a server-authentication certificate in the LocalMachine/Personal certificate store. QSDA selects a certificate matching the hostname in the TLS request, falling back to localhost if necessary.

HTTPS Certificate Thumbprint forces a particular certificate when automatic selection does not work. Copy it from Admin > Service Status > SSL Certs. Leave it blank for automatic selection.

Create self-signed certificate creates a certificate for this server when you do not have one, and sets HTTPS Certificate Thumbprint to it. Run the Control Panel as administrator to use it. The certificate is valid for one year, and its private key cannot be exported. QSDA then offers to trust it on this server. Save the configuration and restart the QSDA services to start using it.

Before creating the certificate, the Control Panel lists the names it will cover, one per line. A browser or the CLI accepts the certificate only for a name on this list, so make sure it holds every name users and tools type to reach QSDA. The list starts with the names QSDA detects for this server: its fully qualified names, its short name and localhost. Add any other name, such as a DNS alias, or a fully qualified name the server does not know, like qsda01.example.com. Remove names you don't want. Each entry can be a host name, a wildcard such as *.example.com, or an IPv4 or IPv6 address. You can also separate names with commas, semicolons or spaces. The first name becomes the certificate's subject. Click Create to make the certificate. QSDA rejects entries that are not valid names or addresses and creates nothing until you fix them.

Browsers warn about a self-signed certificate until it is trusted. To trust it on other computers, click Export certificate... to save the public certificate as a .cer file, and distribute it to the Trusted Root Certification Authorities store on those computers, for example with Group Policy.

The Control Panel warns when the selected certificate is missing or expires within 30 days. To renew a self-signed certificate, create a new one and distribute it again. The old certificate stays in the certificate store until you remove it.

Minimum TLS Version sets the oldest TLS version the UI accepts over HTTPS. TLS 1.2 and 1.3, the default, refuses TLS 1.0 and 1.1. TLS 1.3 only requires Windows Server 2022 or Windows 11 or later, and clients that support TLS 1.3. Operating system default uses the versions Windows enables. Cipher suites always follow the Windows settings; see the Hardening Guide.

Collection queue and memory​

Max Concurrent Collections defaults to 2. Additional requests wait until a running collection frees a slot.

Max Queued Collections defaults to 10. New requests are rejected when the queue reaches its limit.

Idle Hours Limit or 0 controls automatic unloading of idle analyses. Unloading frees analysis memory but retains the stored collection. 0, the default, disables the site-wide idle timeout. QSDA checks for idle collections every 15 seconds, and also when starting or loading collections. The last analysis reference or analysis completion, whichever is later, is used to measure inactivity. Browser and API use can refresh that reference.

A per-collection API timeout overrides the site-wide idle limit. Collections loaded on demand with CLI --load use a 30-second timeout and can be unloaded on a later sweep even when Idle Hours Limit is 0. Opening the collection in the browser overrides the CLI time limit and restores the site limit.

Analysis CPU Limit defaults to 80. It is used to calculate a per-analysis parallelism target from the machine's processor count; it is not a hard percentage cap on Windows CPU usage. Reduce it if concurrent analyses affect other work on the server.