StreamElement alerts not consistently working

Jamin

New Member
Hey there,

So I was dealing with StreamElement's support and they told me to come here because the alert works fine and they said there is an issue on the OBS side. Long story short, the alerts do not consistently work. Sometimes they work, sometimes they do not work at all, and sometimes the video plays but the audio does not.

I took a gander at a log and noticed there's a lot of report errors with my StreamElement alert source. Errors like:
  • [obs-browser: 'Alert - StreamElements'] Error: [Report Only] Refused to connect to 'https://api.streamelements.com/science/insert/overlays' because it violates the following Content Security Policy directive: "connect-src 'none'".
  • [obs-browser: 'Alert - StreamElements'] Error: [Report Only] Refused to connect to 'wss://irc-ws.chat.twitch.tv/' because it violates the following Content Security Policy directive: "connect-src 'none'".
  • [obs-browser: 'Alert - StreamElements'] Error: [Report Only] Refused to load the script 'https://www.redditstatic.com/ads/pixel.js' because it violates the following Content Security Policy directive: "script-src 'none'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.
I'm a bit unclear as to what is going on, and any sage wisdom would be greatly appreciated.

Here is the log: https://obsproject.com/logs/7WAckYJrZxpoSlsJ
 

Suslik V

Active Member
The behavior very similar to: https://obsproject.com/forum/thread...p-didnt-work-after-updating-to-obs-28.159343/
(maybe it has some useful info for you)

The scripts on the pages you visit attempts to alternate the CSP but it seems that it fails similar to:
https://github.com/PhilGrayson/chrome-csp-disable/blob/79371297b6a1f88d1142450dfbd5e85f7e7d9307/background.js#L19-L21 said:
...
// Sites that use Application Cache to cache their HTML document means this
// extension is not able to alter HTTP response headers (as there is no HTTP
// request when serving documents from the cache).
...
(it is my own guess and I may be wrong here)

In case you wish to test (locally) your OBS Browser source page permissions you can try this obs-test-ContentSecurityPolicy-javascript.html code (under the spoiler) from: https://obsproject.com/forum/thread...t-play-music-in-headphones.164572/post-604343
 

PaiSand

Active Member
Any issue with a third party app or service must be asked to that particular app or service provider.
 

Lawrence_SoCal

Active Member
Hey there,
So I was dealing with StreamElement's support and they told me to come here because the alert works fine and they said there is an issue on the OBS side.
StreamElements is a PoS code-wise, and their support person, unfortunately, blew you off /mis-directed you
Good luck
 
Top