You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When trying to connect to a Snapcast server over HTTPS, the control connection appears to be correctly established over https (or wss?), but the stream connection is always set to use ws.
From a quick look in Dev Console, it sees that the ssl prop for the <Stream> component is never populated and is undefined.
If I understand properly, this could be resolved by adding a ssl field to the snapcast state in js/store/index.js?
To Reproduce
Steps to reproduce the behavior:
Serve up Iris and the Snapcast server via an HTTPS server.
Configure Snapcast and click "Streaming enabled"
Expected behavior
The stream should start playing in the browser.
I've confirmed that setting ssl to true via the debugger properly connects to the stream.
Console log
(relevant bit)
Uncaught DOMException: The operation is insecure. SnapStream.tsx:853:6
connect SnapStream.tsx:853
SnapStream SnapStream.tsx:821
Stream Stream.js:27
Stream Stream.js:12
Environment details:
OS: Linux
Browser: Firefox
Iris version: 3.59.1
The text was updated successfully, but these errors were encountered:
Mixed Content: The page at 'https://iris.foo.bar/iris/queue' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://iris.foo.bar:443/stream'. This request has been blocked; this endpoint must be available over WSS.
Describe the bug
When trying to connect to a Snapcast server over HTTPS, the control connection appears to be correctly established over
https
(orwss
?), but the stream connection is always set to usews
.From a quick look in Dev Console, it sees that the
ssl
prop for the<Stream>
component is never populated and isundefined
.If I understand properly, this could be resolved by adding a
ssl
field to thesnapcast
state injs/store/index.js
?To Reproduce
Steps to reproduce the behavior:
Expected behavior
The stream should start playing in the browser.
I've confirmed that setting
ssl
totrue
via the debugger properly connects to the stream.Console log
(relevant bit)
Environment details:
The text was updated successfully, but these errors were encountered: