RemoteDisconnected(“Remote end closed connection without” http.client.RemoteDisconnected: Remote end closed connection without response

Question

Since Google denies access to API key of Google MyBusiness to all but established firms, I attempted to automate the process of changing my business information using seleni

Answer 1

These error messages...

    RemoteDisconnected("Remote end closed connection without"
http.client.RemoteDisconnected: Remote end closed connection without response

and

    RemoteDisconnected("Remote end closed connection without"
urllib3.exceptions.ProtocolError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response',))

...implies that the Remote Connection was disconnected due to ProtocolError.

As per urllib3.exceptions.ProtocolError: ('Connection aborted.', error(10054, 'An existing connection was forcibly closed by the remote host')) This issue is pretty evident when there is a incompatibility between the version of the binaries you are using.

As you are using ChromeDriver and Chrome Browser you must ensure that the binaries are compatible as per the entries below:

• ChromeDriver v2.46: Supports Chrome v71-73
• ChromeDriver v2.45: Supports Chrome v70-72
• ChromeDriver v2.44: Supports Chrome v69-71 (same as ChromeDriver 2.43, but with additional bug fixes)
• ChromeDriver v2.43: Supports Chrome v69-71
• ChromeDriver v2.42: Supports Chrome v68-70
• ChromeDriver v2.41: Supports Chrome v67-69
• ChromeDriver v2.40: Supports Chrome v66-68
• ChromeDriver v2.39: Supports Chrome v66-68
• ChromeDriver v2.38: Supports Chrome v65-67
• ChromeDriver v2.37: Supports Chrome v64-66
• ChromeDriver v2.36: Supports Chrome v63-65
• ChromeDriver v2.35: Supports Chrome v62-64
• ChromeDriver v2.34: Supports Chrome v61-63
• ChromeDriver v2.33: Supports Chrome v60-62
• ChromeDriver v2.32: Supports Chrome v59-61
• ChromeDriver v2.31: Supports Chrome v58-60
• ChromeDriver v2.30: Supports Chrome v58-60
• ChromeDriver v2.29: Supports Chrome v56-58
• ChromeDriver v2.28: Supports Chrome v55-57
• ChromeDriver v2.27: Supports Chrome v54-56

Note: A few months ago, Chromium Team made a preliminary announcement that ChromeDriver's versioning model will be changing. Now we are moving forward with the plan. Specifically, ChromeDriver 2.46 will be the last release carrying the major version of 2. Future ChromeDriver releases will carry a version number similar to Chrome release. We will start with a release of ChromeDriver 73 next week, before the Beta release of Chrome 73.

Here is how the new release model will work:

• ChromeDriver will be using the same version number scheme as Chrome. See https://www.chromium.org/developers/version-numbers for more details.
• Each version of ChromeDriver will support Chrome with matching major, minor, and build version numbers. For example, upcoming ChromeDriver 73.0.3683.* will support all Chrome versions that start with 73.0.3683.
• Before a new major version of Chrome goes to Beta, a matching version of ChromeDriver will be released. For example, a new version of ChromeDriver will be release next week to match the Beta release of Chrome m73.
• After the initial release of a new major version, we will release patches as needed. These patches may or may not coincide with updates to Chrome.