11/19/2026
vMix Web Browser Input Blank on Self-Signed HTTPS
Short answer: If a vMix Web Browser input pointed at a local https:// page stays blank, with an empty thumbnail and nothing on the output, suspect a self-signed certificate. In my test, the same page showed up in vMix as soon as it was served over plain http://. The fix that worked was a second, plain-HTTP port that serves only the pages vMix loads, while the secure port keeps everything else.
The symptom
vMix's Web Browser input loads a URL and treats the page as a video source. Mine pointed at the live score overlay of High Score Live, a scoreboard-reading app from Next Day Videos that serves its pages over HTTPS with a certificate it makes for itself.
What I saw:
- The input's thumbnail stayed blank.
- Nothing showed on the output.
- vMix gave no hint why.
The app had only ever been tested in OBS Studio. The vMix steps in its docs had been written on 09/26/2026 without being run, because vMix was not installed on the machine where Claude Code built the score feed. So I installed vMix and ran the test myself while Claude Code coached me through it.
This is the mirror image of a 403 that is not a broken link: there the server turned the client away, here the client turns the server away, and in both the page itself is fine.
Why it is probably the certificate
vMix's Web Browser input is built on the Chromium Embedded Framework (CEF), and vMix's guide says it has most of the features of Google Chrome. The guide's page for the input lists the URL, size, CSS and keyboard settings. It says nothing about certificates and lists no option to accept one.
CEF leaves the decision to the application that embeds it. The CefRequestHandler documentation says the certificate-error callback can continue or cancel a request, and "Return false to cancel the request immediately." What vMix's handler does is vMix's choice, and a blank input is consistent with a cancelled request.
| Same page in a vMix Web Browser input | What happened |
|---|---|
https://, self-signed certificate |
Blank thumbnail, nothing on output |
http://, no certificate |
The scoreboard showed at once |
One caveat: I changed the protocol and the certificate in the same step. I did not test an HTTPS page with a certificate vMix would trust, so "self-signed certificate" is the best explanation, not a proven one.
Confirm it in two minutes
curl can tell you whether your certificate is the untrusted kind, which is the precondition. On Windows (curl 8.19.0, Schannel), against a local server with a self-signed certificate:
curl -sS -o /dev/null https://localhost:PORT/
# curl: (60) schannel: SEC_E_UNTRUSTED_ROOT ... (exit code 60)
curl -sS -k -o /dev/null -w "%{http_code}\n" https://localhost:PORT/
# 200 (-k skips verification)
Swap in your app's secure port for PORT. Exit code 60 means curl could not verify the certificate; curl's SSL certificate documentation explains why. Add -f in scripts, as in curl exits 0 on a 404.
That tests curl, not vMix. The check that matters is a second vMix input pointed at a plain http:// address of the same page. vMix's own guide uses an http:// address as its example URL. If that input shows the page and the https:// one stays blank, you have the same problem I had.
The fix: a second port for outputs only
In High Score Live, the fix was a second listener, not a new certificate. Turning HTTPS off everywhere was not an option, because phones need HTTPS to use their cameras. MDN's secure contexts page and its getUserMedia page say camera access works only in a secure context: a page loaded over HTTPS, from localhost or from a file URL.
So the app now answers on two ports:
| Page | Secure port (HTTPS) | Plain port (HTTP, 62082) |
|---|---|---|
| Operator dashboard | Served | Refused |
| Phone camera pages | Served | Refused |
| Score overlay | Served | Served |
| Program feed | Served | Served |
| Score data feed | Served | Served |
The dashboard's Copy URL and Add to OBS buttons now hand out the plain address. If the plain port is taken, the app logs a warning and falls back.
Two gotchas on the way
A dashboard tab I had left open on the old https:// address started showing "Failed to update live overlay state". The server had not broken. That tab was speaking TLS to a port now answering plain HTTP, and the app's log showed only invalid-request warnings. Close the tab and open the new address.
Also, a leftover copy of the app from the earlier run was still holding the port. It had to be ended by hand, as that single process, before the restart.
What to put on the plain port
Plain HTTP is not encrypted, so anything on that port can be read by other devices on the same network. Treat it as a read-only window for broadcast software:
- Serve only the output pages and their data feeds.
- Refuse everything else by default, so a forgotten route never ends up on the open port.
- Test the refusal. High Score Live got 14 new tests, and deliberately switching the path filter off made seven of them fail.
If an AI assistant writes that filter for you, read it. The allow-list is the one piece where a mistake exposes your admin pages, and a review is the cheapest place to catch it.
If vMix runs on the same machine as the app, you could bind the plain listener to the loopback address only, which keeps it off the network entirely. I have not tried that with vMix.
OBS Studio and the others
OBS Studio was the only software High Score Live had been tested with before this. Over the secure address, OBS needed a one-time certificate-accept step. With the plain address, that step is gone.
That is all I recorded about OBS. I did not test Wirecast, Streamlabs or XSplit, and I have not yet bound a vMix title to the score data feed. If one of them also shows a blank source on an HTTPS page, the same two-input test applies.

Let my Claude help your Claude
If you want a second pair of eyes on how your own setup uses AI-assisted development, that's what this is: me, personally, for AI specifically. Broader business growth and technology consulting is Brandager's own team.
Researched and drafted with AI, then reviewed and edited by the site's editors.