Error 103 (net::ERR_CONNECTION_ABORTED) - Chrome

Solved
Hello,

Since this morning I'm getting this error "Error 103 (net::ERR_CONNECTION_ABORTED): Unknown error" when I go to Facebook, Hotmail... (https) with Chrome and it works on Firefox.
Has anyone ever encountered this error?

Thank you!

Configuration: Windows 7 / Chrome 25.0.1364.97

3 answers

  • Votes
  • Date
  • Descending date
  1. Here is a proposed solution that has already worked for several.
    Hover over each Chrome shortcut and by right-clicking on the shortcut, then on "Properties", at the end of the "Target" field, try to add this argument to the shortcut's execution command line: "--ssl-version-max=tls1".
    Then click "Apply" to confirm this change.
    Then close Chrome and relaunch it.
    This argument prevents the use of TLS v1.1 or v1.2 and therefore enforces TLS v1.
    This behavior indicates that there is likely a piece of equipment (or software) such as a firewall that was blocking TLS v1.1 traffic for Chrome on your PC.
    Presumably, forcing it has reset it and/or added a directive.
    1. Hello

      Tomy, you need to add the line not in the chrome address bar, but in the properties of your shortcut.

      As for me, I tried your Brainstorm method, but nothing changes. The shortcut modification is not even accepted.
      Here is the error message:
      The name "C:\Program Files\Google\Chrome\Application\chrome.exe --ssl-version-max=tls1" specified in the Target field is not valid. Please check that the path and file name are correct.
      I tried different syntax just in case the spaces or dashes were incorrect, but it doesn’t change anything, still the same error message :(
    2. Ok thanks, I set it like this and it works for me:
      "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --ssl-version-max=tls1
      (so after the " )
    3. I looked a little deeper; in the Chrome installation folder, there is a second program called "old_chrome.exe"

      When I launch that one, it works fine. So I'm using "old_chrome.exe" now and have no issues.

      Thanks for your responses, Tomy and Brainstorm.
    4. thank youuuuuuu