Failed to construct 'WebSocket': The URL 'ws://:61948/' is invalid
See original GitHub issueFor whatever reason the hot-loader is not recognizing my hostname. I’m also not able to populate HMR_HOSTNAME, although I have no problem populating other environmental variables using cross-env
🌍 Your Environment
| Software | Version(s) |
|---|---|
| Parcel | 1.6.1 |
| Node | 8.9.1 |
| npm/Yarn | 1.3.2 (yarn) |
| Operating System | Windows 7 x64 |
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Failed to construct 'WebSocket': The URL '[object Object]' is ...
The connection is not happening and getting error Uncaught SyntaxError: Failed to construct 'WebSocket': The URL '[object Object]' is invalid. in the browser ......
Read more >Failed to construct 'WebSocket' - Glitch Support
Hi! I got the following error when trying to deploy my React project: SecurityError: “Failed to construct 'WebSocket': An insecure WebSocket connection may ......
Read more >parcelでelectron向けビルド - os_jupiterの日記 - はてなブログ
Failed to construct 'WebSocket': The URL 'ws://:61948/' is invalid · Issue #856 · parcel-bundler/parcel · GitHub. したがって parcel watch の ...
Read more >Problems with the root websocket support - Newbie
C and ws.htm files give me the error: Uncaught DOMException: Failed to construct 'WebSocket': The URL's scheme must be either 'ws' or 'wss'....
Read more >Failed to construct WebSocket: URL is invalid - Shuffle iT Forum
dominion-webclient-head-1.2.5.min.js:18 Error: Failed to construct 'WebSocket': The URL 'wss://35.157.6.78:-1536' is invalid.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

I’m still getting this error on version 1.9.2, having to use the
--no-hmrflag to avoid it.@devongovett also getting this error on version 1.9.4. @ZachSaucier the same resolution works.