Not able to make ssl connection (https) with internal device.
Reported by
sagarjai...@gmail.com,
May 28 2018
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36
Example URL:
https://192.168.1.246
Steps to reproduce the problem:
1. Can not be reproduced.
2.
3.
What is the expected behavior?
I should be able to view the login page.
What went wrong?
In wireshark logs I can see handshake failure. But I able to get the login page from other system in different virtual machine.
Did this work before? No
Chrome version: 66.0.3359.181 Channel: stable
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 29.0.0.171
-SSL_CONNECT
--> net_error = -100 (ERR_CONNECTION_CLOSED)
+++++++++++
--> error_lib = 33
--> error_reason = 100 file = "../../net/socket/socket_bio_adapter.cc"
,
May 29 2018
sagarjain125@ Thanks for the issue, Adding 'TE-NeedsTriageHelp' label as this issue is related to Network logs and Wireshark tool. Requesting someone from Internals>Network team to look into the issue and help in further triaging. Thanks..
,
May 29 2018
Please collect and attach a chrome://net-export log. Instructions can be found here: https://sites.google.com/a/chromium.org/dev/for-testers/providing-network-details
,
May 31 2018
The issue has been resolved after installing antivirus. I suspect an sslbot virus causing this issue. Anyway ,thanks for your consideration
,
May 31 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 31 2018
Thanks for the followup! Closing the bug, but feel free to file a new one if needed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by susan.boorgula@chromium.org
, May 28 2018