Troubleshooting
Real issues hit during development, with causes and how to check
The overlay link shows a blank/solid black screen in a normal browser
Usually not a bug — this is expected
Every overlay page shows nothing until the control panel tells it to "go live" — e.g. the name tag starts fully transparent (opacity 0) until you click Play on some row. If you've never clicked Play, seeing a blank page when you open the link is correct.
Why does it look "blank/solid black" in a normal browser?
A normal browser window can't actually render a transparent background — there's no "something behind" the browser tab for it to show through, so the renderer fills the transparent area with a solid color instead (white or black, depending on your system's dark mode). But OBS's Browser Source doesn't work that way — it requests a real alpha-channel render surface directly from CEF and composites it straight onto the scene, so it always renders transparency correctly, even though a normal browser makes it look blank.
How to confirm it's actually working: open that module's control panel and try Play/Show on screen. If the overlay updates in response (even though it still looks blank in a normal browser, for the reason above), the WebSocket connection is working correctly — opening it in OBS itself will always show the correct result.
The overlay doesn't update after switching scenes in OBS
Check whether "Shutdown source when not visible" is unticked — if it's ticked, OBS disconnects the Browser Source every time you switch to another scene, then has to reconnect when you switch back, which looks like it "dropped" when it's really just being turned off/on with the scene switch. Untick this option to keep the connection alive at all times.
The overlay link doesn't work / is rejected
The overlay link carries a token unique to your account (?token=...) — if you just clicked "Regenerate overlay link", the old link stops working immediately. Copy the new link into your OBS Browser Source instead (this button exists in case an old link leaked somewhere).