Imploded Software

Helium Streamer can serve its web interface and API over either HTTP or HTTPS. HTTPS is configured from the Streamer Launcher app, on the Settings page, and applies to the Streamer service (Streamer.Api) that the launcher manages.

Where to find the setting

1. Open Streamer Launcher.
2. Go to the Settings page.
3. Tick Use HTTPS to enable secure connections, or leave it unticked to serve the web interface over plain HTTP.
4. Choose one of the three certificate options described below, then click Apply.

Note: Streamer uses a single port for both HTTP and HTTPS - you don't configure separate ports for each. Whichever scheme is selected determines how that port behaves. The default port is 3030, but the installer will pick the next free port automatically if 3030 is already in use.

Certificate options

When Use HTTPS is enabled, choose one of the following certificate sources:

1. Self-signed certificate (default, recommended for most users)

• Streamer automatically generates and manages a self-signed TLS certificate - no setup required.
• The certificate covers localhost, your computer's machine name, and all detected local/external IP addresses, so it works whether you connect from the same machine or from another device on your network.
• It is valid for 10 years and is automatically regenerated if it's about to expire (within 30 days) or if your machine's IP addresses change (e.g. after moving networks).
• Browser warning: because the certificate is self-signed, browsers will show an "untrusted certificate" warning the first time you connect. Click the Trust Certificate button on the Settings page to install the certificate into Windows' trusted root store - this removes the warning on that computer. Fully restart your browser and reload the page afterwards for it to take effect.
• If Trust Certificate reports no certificate was found, make sure HTTPS is enabled and Apply has been clicked, and that the Streamer service has started at least once — then try again after a moment.

2. PFX certificate file (bring your own certificate)

• Choose this if you already have a certificate issued by a certificate authority (e.g. for a public domain name) or otherwise want to supply your own.
• Click Browse and select a certificate file in PKCS#12 (.pfx) format. PEM/CRT/CER files are not supported directly - convert them to .pfx first if needed.
• If the certificate is password-protected, enter the password in the field provided. The password is stored encrypted.
• On Apply, Streamer Launcher validates that the file exists and can actually be loaded with the supplied password. If loading fails, you'll see: "The certificate file could not be loaded. Please check the file and password."

3. Windows Certificate Store

• Choose this to use a certificate that is already installed on this computer.
• Only certificates that are currently valid and have an accessible private key are listed, and they must be located in the Local Machine → Personal (My) store.
• Select the desired certificate from the list. If your certificate doesn't appear, confirm it was imported into Local Machine\Personal, not Current User\Personal, and that its private key is marked exportable/accessible.
• If the certificate is later removed from the store (or the service can't find it by thumbprint), the Streamer service will fail to start with an error referencing the missing certificate thumbprint.

Important notes

• Let's Encrypt / ACME is not supported. There is no automatic domain-validated certificate issuance - only self-signed, manually supplied PFX files, or certificates already present in the Windows certificate store.
• Port conflicts: if the chosen port is already in use by another application, Apply will be blocked with a message asking you to choose a different port.
• Applying changes: clicking Apply saves the configuration and restarts the Streamer service so the new settings take effect.
• No password required: the PFX password field can be left blank if your certificate file has no password (this is normal for the automatically generated self-signed certificate).

Troubleshooting