UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.181 Safari/537.36

Steps to reproduce the problem:
have a webpage that opens a websocket over wss:// .
Look in Developer Tools->Security The wss connection will show up, but there are no security details for it.

What is the expected behavior?
Should be able to see certificate received from the server, and view details of certificates.

What went wrong?
wss:// shows up under 'Unknown/Canceled' connections instead of 'Secure Origins'. 
While writing this, I went to 'https://youtube.com' to see security info there, and it has several other https:// references which show up and are browsable with security information.

Did this work before? No 

Chrome version: 65.0.3325.181  Channel: stable
OS Version: 10.0
Flash Version: 

My application loads from a webserver (html/js), and uses websockets to connect to a different server, using wss.  This second connection is using our own certificate chain, which means I have to connect to that server over https:// and then I can accept that certifcate as valid, then the wss:// connection works.  (although it does have a default-accept-bad-cert sort of option enabled).  This websocket connection gets a redirect to one of many other servers also using wss:// but since that is a different IP is a different certificate.  (but since it's still on the same host, for now, the default accept is still working).  I can communicate on this second websocket; and perform a login, and service request, on the service request, I get another address and port to connect to.  This third redirection is failing.,,,

VM190:164 WebSocket connection to 'wss://...:13616/' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

I would like to be able to see the certificate information to see if it really is invalid, or if this third redirectly through temporarily valid sockets is what's failing...  But; none of the wss connections show their certificate information.

In the normal application, which includes the root certificate to complete the chain, I have no issue connecting to the same services.  but this is about the lack of information; not the failure.