ETIMEDOUT on running protractor tests on a remote selenoid or selenium standalone

[StanislavKharchenko]

🐛 Bug Report

During run test case on protractor using any selenium remote machine (it could be selenium standalone, or selenoid) the following error occurs from time to time:

ETIMEDOUT connect ETIMEDOUT xx.xx.xx.xx:443
          at ClientRequest.<anonymous> (/workdir/node_modules/selenium-webdriver/http/index.js:238:15)
          at emitOne (events.js:116:13)
          at ClientRequest.emit (events.js:211:7)
          at TLSSocket.socketErrorListener (_http_client.js:387:9)
          at emitOne (events.js:116:13)
          at TLSSocket.emit (events.js:211:7)
          at emitErrorNT (internal/streams/destroy.js:64:8)
          at _combinedTickCallback (internal/process/next_tick.js:138:11)
          at process._tickCallback (internal/process/next_tick.js:180:9)Error 

This looks the same issue which was fixed previously: https://github.com/SeleniumHQ/selenium/issues/8129

To Reproduce

Detailed steps to reproduce the behavior:

1. Have a remote grid (selenium or selenoid would make no difference) deployed on the network, but not on your machine.
2. Running those test(-s) should from time to time display errors about ETIMEDOUT

Expected behavior Test(-s) run without this exception

Environment

OS: Windows 10 Browser: Chrome 87.0.4280.66 Language: Javascript protractor 7.0 selenium standalone or selenoid

[diemol]

This is probably because no version had been released since that issue was solved, however, alpha 8 (only for the JS bindings) released yesterday. Please try that version, and feel free to reopen or create a new issue if this persists. https://www.npmjs.com/package/selenium-webdriver/v/4.0.0-alpha.8