UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.108 Safari/537.36

Steps to reproduce the problem:
1. navigate to bank website
2. 
3. 

What is the expected behavior?
should load bank website homepage

What went wrong?
This site can’t provide a secure connection
www.xxxxxx.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

Did this work before? Yes 62.0.3202.94

Chrome version: 63.0.3239.108  Channel: stable
OS Version: Linux Mint 17.3 Rosa 4.4.0-45-generic #66~14.04.1-Ubuntu x86_64 GNU/Linux
Flash Version: Flash Version: 27.0.0.187

When I attempt to log in to mail.aol.com

Chrome presents a page that displays: 
-------------------------------
This site can’t be reached
The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_RESET
-------------------------------

Before updating from 62.0.3202.94 - the page to login would load 

This behavior started after updating to Chrome version: 63.0.3239.84 : Stable and persists in 63.0.3239.108

Firefox 57 continues to load these pages properly

When I re-install google-chrome-stable_62.0.3202.94-1_amd64.deb - I am able to access those sites that failed to connect after the updates ...

Which now include 39 security fixes

When thomasanderson@chromium.org last logged into https://bugs.chromium.org/p/chromium/issues/detail?id=793679 where I report that google-chrome-stable_63.0.3239.84 had impaired my ability to log into various sites - he asked me to bisect the issue and posted terminal commands with a link embedded - but did not explain that those commands would open a Chromium browser window, or that the python tool would also be transmitting data from my PC to ?google?...

Nor did he respond when I asked for guidance regarding the Chromium window or the fact that the terminal was apparently waiting for data from the Chromium window - after I closed the Chromium window, the teminal window resumed with this:

Revision xxxxxx is [(g)ood/(b)ad/(r)etry/(u)nknown/(s)tdout/(q)uit]: 

https://bugs.chromium.org/p/chromium/issues/detail?id=793679 current status is WontFix - and shows as being closed as of Dec 11

I hope that this report will be addressed more effectively - in the meantime - I guess I have no choice but to use Firefox until the chrome team can properly address the issues described