On a development server hosting a web application that can be accessed via http and https (through self-signed unsecure certifcate that needs the browser to force accept the certificate), Firefox won't connect to a secured websocket (via wss) when the webservice is accessed through a self-signed (aka unsecure) https connection.
The websocket works fine in Firefox through http and ws. Yet it won't connect if the web page is accessed through https / wss.
Confusingly, the websocket works on Chrome just fine both through http / ws and https / wss.
In Firefox' dev tools, I see NS_ERROR_NET_RESET.
Researching the issue, I also found this answer, proposing to manually accept the certificate by going to the websocket's url via https, yet I don't see an option to accept the certificate. Instead, I get SSL_ERROR_RX_RECORD_TOO_LONG.
I don't understand what Firefox is really complaining about, and furthermore I am confused why Chrome would just work. (I expected both to not work if the security is not setup correctly; yet keeping in mind this is a local dev server, the certificate need not necessarily be secure, even though this might be best practice. For now, goal is allowing Firefox to access the websocket if the webserver is accessed via https.)
(As of yet, I cannot provide a reproducible example. I try to provide it at a later step.)
Addendum: The websocket is hosted on a specifc port. The url targets:
- wss://<domain>:10000/some-location/
- ws://<domain>:10000/some-location/
respectively. I am not sure if Firefox might want specific ports for secure connection?
