Issue metadata
Sign in to add a comment
|
Failed to load resource: net::ERR_CONNECTION_REFUSED due to self-signed letsencrypt ssl
Reported by
mehmetcu...@gmail.com,
Jan 24 2017
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36 Steps to reproduce the problem: Error is shown on developer console What is the expected behavior? We have a self signed ssl from lets encrypt. After this release we started to get the following error for our api calls to server: net::ERR_CONNECTION_REFUSED What went wrong? Guess smtg is changed with handling of self signed ssl. Did this work before? Yes 57.0.2986.0 Chrome version: 55.0.2883.87 Channel: stable OS Version: Ubuntu 16.04 Flash Version: Shockwave Flash 24.0 r0
,
Jan 25 2017
,
Jan 25 2017
(If you have something from Let's Encrypt it's probably not self-signed.) Please attach a net-internals log per these instructions. Thanks! https://dev.chromium.org/for-testers/providing-network-details
,
Jan 25 2017
ERR_CONNECTION_REFUSED doesn't seem likely to be an SSL issue, since we only get that from the OS's socket on connection, before we've even gotten any data from the server. Looking at the log, every connection to lethalbet.com:8443 (192.241.142.163) is refused. Unless we're connecting to the wrong server or IP address, doesn't look like a Chrome issue.
,
Jan 25 2017
We're not getting far enough to even send a ClientHello. The server is refusing a TCP connection? Are you sure that server is even running on port 8443? Does it work in other browsers?
,
Jan 30 2017
mehmetcubuk: Could you answer davidben's question? This is looking a lot like a server issue, since Chrome can't even establish a TCP connection to the server.
,
Jan 30 2017
The server is listening on 8443 but for some reason can't receive requests from the browser. We changed the architecture to use a subdomain to make the request which works.
,
Jan 30 2017
Thanks for the followup! I'm going to go ahead and mark this WontFix. If you have some reason to still believe Chrome is at fault here, happy to reopen. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by chrishtr@chromium.org
, Jan 25 2017