I wanted to try out some Websocket endpoint for my application and I downloaded the Chrome extension, but when I tried it, I ran into the following error as can be seen from the screenshot below:
Any ideas as to how I could get it fixed?
Related
I have to connect to Socket.IO server from my app.
I'm using Angular wrapper ngx-socket-io without any special options set.
I have noticed that everything works when I'm connecting in incognito mode - in regular mode I get "cannot connect exception".
I was compering requests in Chrome Dev console and I haven't seen any difference between them.
Have anyone noticed similar issues ?
I have a domain x.com which is running a web application
There is an MQTT server running on subdomain mqtt.x.com, with websockets / wss all set up,
Using Chrome:
If I head to https://x.com, and run this in console:
let ws = new WebSocket('wss://mqtt.x.com')
I get the following error:
WebSocket connection to 'wss://mqtt.x.com/' failed:
If I go to a completeley different domain (such as stackoverflow.com) and run the command, it works fine.
In firefox/opera/edge, no errors, and it all works fine.
Is there any way to get a more verbose error from chrome?
Or any other idea to resolve this?
Edit
Clearing cookies seemed to solve this. still not really sure why.
Clearing Cookies seemed to be the answer.
Web.dev shows that there are console errors from third party tracking software (LuckyOrange):
WebSocket connection failed: Error in connection establishment:
net::ERR_NAME_NOT_RESOLVED.
Tried to reproduce same error with Lighthouse in Chrome DevTools, also with Lighthouse CLI, Headless Chrome. Was unable to do that. There are no errors in browser console too.
Maybe somebody have experienced the same issue?
I have experience with this. I have always ignored these warnings as they are inconsistent. I THINK they are caused by my CDN blocking the automated requests, resulting in console errors. For me it happens every now and then and only after repeated querying.
Note that I have no proof for this theory.
I am facing an issue in connecting to websocket. For a simple test i opened this url http://www.websocket.org/echo.html and clicked connect. I am getting error undefined.
Browser using chrome. I also tested in IE and firefox still the problem is same.
Can any one please help me whats wrong with my laptop. Till yesterday i was able to make websocket connect successfully but after my windows 10 updates now i am unable to make connection.
No sweat. ws://echo.websocket.org is down.
I'm developing several sites that I just install certs on. Chrome (Version 42.0.2311.135 m) is reporting an error that "This page is trying to load scripts from unauthorized sources". I don't get any error in IE or FireFox.
Page I'm seeing the error
It seems like I'm getting mixed results with (secure) embedded content since going to SSL.
Thanks for any guidance you can provide.
Dave