appium: Appium - Could not proxy command to remote server

Objective:

I am trying to run a Calculator app – on windows 10.

Environment

Appium - V1.7.1 Windows 10 WinAppDriver: 0.9 beta

Details

Could not proxy command to remote server comes up when i try run from eclipse - with above code

Appium logs

] Welcome to Appium v1.7.1 [Appium] Appium REST http interface listener started on 0.0.0.0:4723 [HTTP] --> POST /wd/hub/session {“desiredCapabilities”:{“app”:“Microsoft.WindowsCalculator_8wekyb3d8bbwe!App”,“deviceName”:“WindowsPC”,“platformName”:“Windows”},“capabilities”:{“desiredCapabilities”:{“app”:“Microsoft.WindowsCalculator_8wekyb3d8bbwe!App”,“deviceName”:“WindowsPC”,“platformName”:“Windows”},“firstMatch”:[{“platformName”:“windows”}]}} [debug] [MJSONWP] Calling AppiumDriver.createSession() with args: [{“app”:“Microsoft.WindowsCalculator_8wekyb3d8bbwe!App”,“deviceName”:“WindowsPC”,“platformName”:“Windows”},null,{“desiredCapabilities”:{“app”:“Microsoft.WindowsCalculator_8wekyb3d8bbwe!App”,“deviceName”:“WindowsPC”,“platformName”:“Windows”},“firstMatch”:[{“platformName”:“windows”}]}] [debug] [BaseDriver] Event ‘newSessionRequested’ logged at 1512675085174 (13:31:25 GMT-0600 (Central Standard Time)) [Appium] Creating new WindowsDriver (v0.5.0) session [Appium] Capabilities: [Appium] app: ‘Microsoft.WindowsCalculator_8wekyb3d8bbwe!App’ [Appium] deviceName: ‘WindowsPC’ [Appium] platformName: ‘Windows’ [BaseDriver] The following capabilities were provided, but are not recognized by appium: app. [BaseDriver] Session created with session id: 7eb10048-31e6-4792-8533-c2f08f8b2170 [WinAppDriver] Verifying WinAppDriver is installed with correct checksum [debug] [WinAppDriver] WinAppDriver changed state to ‘starting’ [WinAppDriver] Killing any old WinAppDrivers on same port, running: FOR /F “usebackq tokens=5” %a in (netstat -nao ^| findstr /R /C:"4724 ") do (FOR /F “usebackq” %b in (TASKLIST /FI "PID eq %a" ^| findstr /I winappdriver.exe) do (IF NOT %b==“” TASKKILL /F /PID %a)) [WinAppDriver] No old WinAppDrivers seemed to exist [WinAppDriver] Spawning winappdriver with: undefined 4724/wd/hub [WinAppDriver] [STDOUT] Windows Application Driver Beta listening for requests at: http://127.0.0.1:4724/wd/hub [debug] [WinAppDriver] WinAppDriver changed state to ‘online’ [debug] [JSONWP Proxy] Proxying [POST /session] to [POST http://127.0.0.1:4724/wd/hub/session] with body: {“desiredCapabilities”:{“app”:“Microsoft.WindowsCalculator_8wekyb3d8bbwe!App”,“deviceName”:“WindowsPC”,“platformName”:“Windows”}} [WinAppDriver] [STDOUT] Press ENTER to exit. [JSONWP Proxy] Got unexpected response: <HEAD><TITLE>Connection refused</TITLE></HEAD>

<BODY BGCOLOR="white" FGCOLOR="black">

Connection refused


<FONT FACE="Helvetica,Arial"> Description: Connection refused</FONT>
</BODY> ... [debug] [WinAppDriver] Deleting WinAppDriver session [MJSONWP] Encountered internal error running command: ProxyRequestError: Could not proxy command to remote server. Original error: 502 - "<HEAD><TITLE>Connection refused</TITLE></HEAD>\n<BODY BGCOLOR=\"white\" FGCOLOR=\"black\">

Connection refused


\n<FONT FACE=\"Helvetica,Arial\">\nDescription: Connection refused</FONT>\n
\n\n</BODY>\n \u0000" at JWProxy.proxy$ (../../../lib/jsonwp-proxy/proxy.js:152:13) at tryCatch (C:\Users\a150400\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:67:40) at GeneratorFunctionPrototype.invoke [as _invoke] (C:\Users\a150400\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:315:22) at GeneratorFunctionPrototype.prototype.(anonymous function) [as throw] (C:\Users\a150400\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:100:21) at GeneratorFunctionPrototype.invoke (C:\Users\a150400\AppData\Roaming\npm\node_modules\appium\node_modules\babel-runtime\regenerator\runtime.js:136:37) [HTTP] <-- POST /wd/hub/session 500 457 ms - 915

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 34 (11 by maintainers)

Most upvoted comments

I assume the problem has been fixed