Unable to connect to chrome-devtools-frontend.appspot.com:80

[anifox2]

Everytime I try to connect to Safari on my iPhone 6S, I can see my device in the list and my open tabs but when i press a tab, I get this error message:

Unable to connect to chrome-devtools-frontend.appspot.com:80

I am running Chrome 50 on Windows 8.1 and using ios-webkit-debug-proxy-mingw32

[artygus]

@anifox2 mingw build is not production ready yet, please try "-f http://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html". Chrome dev protocol went too far from what Safari has and latest dev tools wouldn't show you styles at all (at least it didn't work 3-4 months ago), I suggest using dev tools extracted from webkit https://github.com/artygus/webkit-webinspector

[anifox2]

I have already tried https://github.com/artygus/webkit-webinspector and I'm just getting a white page. Using "-f http://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html" gives me the same error message: Unable to connect to chrome-devtools-frontend.appspot.com:80

[artygus]

@anifox2 hm, then you can try to run ios_webkit_debug_proxy -F and then navigate to https://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html?ws=localhost:9222/devtools/page/1 in your browser

[anifox2]

1. If I use the normal "ios-webkit-debug-proxy-win32" i get this error when starting it with "ios-webkit-debug-proxy.exe -F":
   Invalid message _rpc_reportConnectedApplicationList:
   WIRApplicationDictionaryKey
   
   PID:409
   
   WIRApplicationIdentifierKey
   PID:409
   WIRIsApplicationProxyKey
   
   WIRApplicationNameKey
   Safari
   WIRApplicationBundleIdentifierKey
   com.apple.mobilesafari
   WIRIsApplicationActiveKey
   1
   
   PID:411
   
   WIRApplicationIdentifierKey
   PID:411
   WIRIsApplicationProxyKey
   
   WIRApplicationNameKey
   
   WIRApplicationBundleIdentifierKey
   com.apple.WebKit.WebContent
   WIRIsApplicationActiveKey
   1
   WIRHostApplicationIdentifierKey
   PID:409
   
   PID:71
   
   WIRApplicationIdentifierKey
   PID:71
   WIRIsApplicationProxyKey
   
   WIRApplicationNameKey
   
   WIRApplicationBundleIdentifierKey
   lockdownd
   WIRIsApplicationActiveKey
   1
   
   
   
   

And when trying to connect to https://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html?ws=localhost:9222/devtools/page/1 I get these two error messages (if I open developer tools on the site):

DevTools.js:3104 Mixed Content: The page at 'https://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html?ws=localhost:9222/devtools/page/1' was loaded over HTTPS, but attempted to connect to the insecure WebSocket endpoint 'ws://localhost:9222/devtools/page/1'. This request has been blocked; this endpoint must be available over WSS.WebInspector.loaded @ DevTools.js:3104windowLoaded @ DevTools.js:3302
DevTools.js:3104
Uncaught SecurityError: Failed to construct 'WebSocket': An insecure WebSocket connection may not be initiated from a page loaded over HTTPS.

1. If I open "ios-webkit-debug-proxy-mingw32" using ios_webkit_debug_proxy.exe -F, I do not get any errors until I open https://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html?ws=localhost:9222/devtools/page/1. Then I get the same security error described above in the js console (if I open developer tools)

[anifox2]

In both cases, https://chrome-devtools-frontend.appspot.com/static/27.0.1453.93/devtools.html?ws=localhost:9222/devtools/page/1 is just a blank page with a grey bar at the top with 3 unclickable buttons and a light grey bar at the bottom except the errors in the console.

[artygus]

@anifox2 just click on the shield icon https://github.com/artygus/ios-webkit-debug-proxy-win32#troubleshooting

[anifox2]

That worked! Thank you!

[galziv]

Hi, the solution worked for me, but the devtool is very old and doesn't have websocket tab in the network panel which I really need.
Which other version than '27.0.1453.93' is valid?

[artygus]

hi @galziv check out alternatives to chrome devtools here https://github.com/google/ios-webkit-debug-proxy#devtools-note, if you're stuck with chrome dev tools, you could try http://frontend.chrome-dev.tools/serve_rev/@198714/inspector.html

[galziv]

thanks for the prompt answer! i'll take a look