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
Related
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?
I have a problem regarding opening http://review.jow.medknow.com/abr in chrome.
The page works fine in the Firefox browser but does not load completely in the chrome browser, even in incognito mode.
Using inspect, I found that https://uniprrapi.digiscapetech.com/ failed to load in chrome.
I also should mention that the problem is only by some of Iran's IPs.
Could anyone help me that how I can solve this problem?
Recently i found out that after resizing my chrome browser during testing with the inspector open, my address / URL bar disappears unfindable. although while opening a new tab i can enter URLs normally since the url bar gets autofocused, but the bar is still invisible. Does anybody know why this happens or how to disable this feature / bug.
Has anybody else seen this before, or is it just me?
Help appreciated, thx
I've had the same issue as of late. While I have not found a solution in the Chrome stable channel, switching over to Chrome Canary seems to be a valid interim fix. Of course, there could be some bug happening in one of my extensions that aren't present, but this is allowing me to get some work done.
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'm using Chrome-compatible SRWare Iron 5.0.381 on XP, and was checking out what Chrome has to offer to developers, EG inspecting the contents of the DOM of a currently-loaded web page.
But when I hit CtrlShiftI, the bar is totally empty:
Does someone why this is? Do I need an add-on? Are there other Chrome-compatible tools I should know about?
It appears you’ve found a bug in that fork of Chromium. The inspector works just fine with Google.fr in the latest Google Chrome and Chromium builds. Why don’t you use one of these browsers.
Usually the reason of that is some problem in DevTools JS code.
It is a chance that problem will be solved by chrome restart.
Such kind of problems can happen when chrome is upgrading at background.
The other reason of that can be some changes which you made in DevTools.js.
Of cause if you have done some changes :)
You can troubleshoot such problem by another instance of DevTools.
As example you can try to load DevTools.html page into Safari, open WebInspector for it and check console messages.