SSL issues with Chrome 73.0.3683.86

187 views
Skip to first unread message

dir Ls

unread,
Mar 26, 2019, 12:13:30 PM3/26/19
to Google App Engine
Ever since I upgraded Chrome to 73.0.3683.86, I am not able to connect to the local app server using SSL (self signed). Any one having this issue?

Safari, Firefox and MS Edge work fine.

I get the following error.

Exception in thread WSGI select:
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
    self.run()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/Users/me/google-cloud-sdk/platform/google_appengine/google/appengine/tools/devappserver2/wsgi_server.py", line 166, in _loop_forever
    self._select()
  File "/Users/me/google-cloud-sdk/platform/google_appengine/google/appengine/tools/devappserver2/wsgi_server.py", line 188, in _select
    fd_to_callback[fd]()
  File "/Users/me/google-cloud-sdk/platform/google_appengine/lib/cherrypy/cherrypy/wsgiserver/wsgiserver2.py", line 1902, in tick
    s, ssl_env = self.ssl_adapter.wrap(s)
  File "/Users/me/google-cloud-sdk/platform/google_appengine/lib/cherrypy/cherrypy/wsgiserver/ssl_builtin.py", line 52, in wrap
    keyfile=self.private_key, ssl_version=ssl.PROTOCOL_SSLv23)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 911, in wrap_socket
    ciphers=ciphers)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 579, in __init__
    self.do_handshake()
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/ssl.py", line 808, in do_handshake
    self._sslobj.do_handshake()
SSLError: [SSL: SSLV3_ALERT_CERTIFICATE_UNKNOWN] sslv3 alert certificate unknown (_ssl.c:590)

yka...@google.com

unread,
Apr 9, 2019, 5:06:14 PM4/9/19
to Google App Engine
Hello,

Clearing the cache may solve the issue. But if the issue persists, I recommend posting the error on Stackoverflow as it is better suited for technical issues.

You can also report this to the Chrome Team here since there are no issues with other browsers.
Reply all
Reply to author
Forward
0 new messages