I tried to take turing test with my chrome browser. I have got unexpected chrome is not responding alert. My chrome is working for any websites till now but Turing.
I tried to update chrome twice, but seems not working.
Anyone who can help me, please?
Related
I want to attach puppeteer to chrome, but that straight forward.
The problem is this doesn't work:
start chrome.exe --remote-debugging-port=9222
This runs and opens chrome as expected. The problem is not in debug mode. This should open a JSON on the browser:
127.0.0.1:9222/json/version
I have tried a lot already and it doesn't seem to work. Anyone knows why?
thank you,
Its not a solution, but after a lot o trying, works perfectly in same way for firefox
start firefox --remote-debugging-port=9229
We are seeing a really weird issue with our production site where after 30 seconds it appears that the session is invalidated in the Chrome and Edge browsers. We don't see any errors in the chrome inspect console.
We saw this behavior on 25MAY2022 right around when chrome 102 got pushed to the browsers at 5pm. IF we use inspect and turn off the cache then we don't see any issues with loading the site and everything operates fine.
FireFox works fine.
I'm using chrome 101.0.4951.61 against the same site on my android 11 phone and I cannot reproduce the issue.
Are there any new features in 102 we could turn off to see if a specific new security check might be at play?
My team is experiencing a similar issue when calling our API. If you go to chrome://flags/#private-network-access-send-preflights, and disable it, does that resolve your issue? If it does, then adding this header to your site may resolve the issue:
Access-Control-Request-Private-Network: true
We are currently doing pre-prod testing which is so far promising.
https://developer.chrome.com/blog/private-network-access-preflight/
Chrome ERROR_TIMED_OUT in latest version
I just noticed this yesterday. My processing sketches on willhay.io have stopped working in Google Chrome and Firefox, however, they work fine in Safari. I haven't changed their code so it is very strange. Console is giving me this error
GET http://willhay.io/cdn-cgi/pe/bag2? r[]=http%3A%2F%2Fwillhay.io%2Fprocessing%2Fprocessing.min.js 405 (Not Allowed)
Something to do with Cloudflare maybe (I've just got the free version)? Check it out for yourself here:
http://willhay.io/processing/trip/
Turns out it was CloudFlare and the way their RocketLoader page speed optimizer works. I just turned it off after remembering I switched it on the other day and the Processing sketches are now working fine. Had something to do with the way it messes with the javascript and I guess processing.js didn't like that.
Strange behavior.
This site: ****
Works in firefox and internet explorer, despite the insecure certificate.
But doesn't work at all in Chrome, and says ERR_CONNECTION_ABORTED
Anyone else getting this? I've tried it on 3 different computers already, and can't figure out why Chrome doesn't see it. Also, I can't get it to work on an iphone either.
How do I get this to work in all browsers, am I doing something wrong? Someone help
It is possible that Microsoft Update KB2992611 is causing the problem. See this article: http://www.infoworld.com/article/2848574/operating-systems/microsoft-botches-kb-2992611-schannel-patch-tls-alert-code-40-slow-sql-server-block-iis-sites.html
Uninstall the patch solved the problem, but I am not sure of the right steps to take to fix what the patch was intending to fix.
I can get to the site over HTTP, but not over HTTPS (tested in Chrome 38.0.2125.122 and Safari 8.0). Does this help?
I have similar problems begin lately with HTTPS pages of two websites on Win server 2012.
On most computers it works fine.
But in some computers:
In IE FF or Safari its OK,
But in Chrome or new Opera it raise error:
"This webpage is not available
The webpage at [my https url] might be temporarily down or it may have moved permanently to a new web address."
In Chrome it show also: "Error code: ERR_CONNECTION_ABORTED"
This failed requests not appear in the IIS logs.
I have reported bug, that something doesn't work in IE9. I started IE and I saw that bug, but as soon as I ran developer tools in IE, my bug was gone and everything works well. Unfortunately when I run IE again bug is still.
What is the worst it happens not only for one concrete bug. It happens all the time. So it isn't nature of bug, but IE. It prevents me to debug it. What can I do?
I didn't switch mode of engine in developer tool
My problem was that there is console.log(...) in my code.
Until I don't run developer tools, console doesn't exist and it throws error and my code stops, so rest doesn't work.