Unknown error occurred when trying to connect to Scrypted
gorfreed opened this issue · 5 comments
(Continued from closed Addon should not enforce SSL
Other scripts do not need to enforce SSL and it comes up as possible source of error everywhere, even if it might not be directly involved. For instance, I am now trying a new Home Assistant setup running on VMWare Windows, while running Scrypted Desktop on the same machine in parallel. Both HA in VMWare and Scrypted Desktop work flawlessly on their own, but for some reason I am failing to connect HA with the Scrypted Desktop instance, always receiving an "Unknown error occurred" message.
Upon looking into the HA system logs for possible causes, guess what I find:
I have no clue whether this is actually whats causing the error, but I feel any error with Scrypted has a high likelyhood to be SSL related, especially considering anything else on HA runs without certificates.
Note: Port 11080 has been cleared in the Windows Firewall
you're trying to use the insecure port.
No I am not. I am using YOUR default settings without any customization, set up as per your documentation. As others have pointed out elsewhere, your software decided to use 11080 instead of the one in your documentation for reasons unknown.
I suggest for you to stop closing unresolved issues.
11080 is the insecure port. 10443 is the secure port. the directions in your screenshot say you must use an HTTPS endpoint. the directions also suggest 10443 (the default) in the screenshot. you customized it to 11080. I didn't do that.
But thats what I am saying, there is NO OPTION to select or customize the port on Scrypted Desktop! Where would I make this choice? Why is the correct one not selected by default?!
But thats what I am saying, there is NO OPTION to select or customize the port on Scrypted Desktop! Where would I make this choice? Why is the correct one not selected by default?!
scrypted desktop will use 10443 for the https port. that's the port you want to enter in the screenshot above (or rather, no port at all as its the implicit default). it is currently not changeable but I'll add an external option to configure it in the next release.
make sure windows firewall is allowing it through. test it in a browser from another PC.