forked from mozilla/BrowserQuest
-
Notifications
You must be signed in to change notification settings - Fork 220
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sign-in Not working #208
Comments
Inspect element and paste your error here. |
Brave Version 1.8.95 Chromium: 81.0.4044.138 (Official Build) (64-bit) |
|
I got this same error when submitting a new character, and it just says "loading" forever. As a work-around, you can replace "https://" with "http://" in the URL. Of course, this is not ideal though, as HTTP is not as secure as HTTPS. |
Uh oh
On Sunday, February 14, 2021, 11:09:31 PM EST, Mark Langer <[email protected]> wrote:
gameclient.js:62 Uncaught DOMException: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.
at Class.connect (https://browserquest.herokuapp.com/js/gameclient.js:62:35)
at Class.connect (https://browserquest.herokuapp.com/js/game.js:759:29)
at https://browserquest.herokuapp.com/js/game.js:698:26
connect @ gameclient.js:62
connect @ game.js:759
(anonymous) @ game.js:698
I got this same error when submitting a new character, and it just says "loading" forever. As a work-around, you can replace "https://" with "http://" in the URL. Of course, this is not ideal though, as HTTP is not as secure as HTTPS.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When one signs in as a new character, you can play. However, when you try to sign in again, it doesn't allow you, by either loading infinetely or repeatedly giving the incorrect password message. This was used on google chrome.
The text was updated successfully, but these errors were encountered: