Open GoogleCodeExporter opened 8 years ago
This looks like you hit a captive portal--were you on guest wifi (possibly run
by Apple) at this point?
See this part of the message:
Server presented certificate that does not match host www.googleapis.com:
{'crlDistributionPoints': (u'http://ss.symcb.com/ss.crl',), 'subjectAltName':
(('DNS', '*.smoot.apple.com'),), 'notBefore': u'Oct 21 00:00:00 2014 GMT',
'caIssuers': (u'http://ss.symcb.com/ss.crt',), 'OCSP': (u'http://ss.symcd.com',
'serialNumber': u'1776B0F5475C499C142D8075C2F7BD9E', 'notAfter': 'Oct 20
23:59:59 2016 GMT', 'version': 3L, 'subject': ((('countryName', u'US'),),
(('stateOrProvinceName', u'California'),), (('localityName', u'Cupertino'),),
(('organizationName', u'Apple Inc.'),), (('organizationalUnitName', u'Siri
SF'),), (('commonName', u'*.smoot.apple.com'),)), 'issuer': ((('countryName',
u'US'),), (('organizationName', u'Symantec Corporation'),),
(('organizationalUnitName', u'Symantec Trust Network'),), (('commonName',
u'Symantec Class 3 Secure Server CA - G4'),))}
Crashing is obviously not the right thing to do here, but I don't think there's
a way around this on the gcloud end.
Original comment by z...@google.com
on 4 Feb 2016 at 10:56
Yes, I was on guest wifi. I don't know if it was an Apple wifi network.
I guess I don't understand the error / what happened. I used the same guest
network earlier in the day and everything worked fine. Also, about 30 minutes
after I encountered this problem, everything seemed to work again.
What should I be doing to avoid this problem in the future? If I see the
problem again, is there anything I can do to work around it?
Original comment by rbusk...@google.com
on 5 Feb 2016 at 10:17
Was it one that you had to click through a terms & conditions page for? My
hunch is that the network "forgot" your connection after a while.
The stack trace indicates that gcloud tried to open an HTTPS connection to
www.googleapis.com, but was presented a bad SSL certificate. This indicates a
network problem of some sort--whether it's a malicious MitM or your WiFi access
point just wants you to click through. I bet, for instance, that `curl
https://www.googleapis.com/` (normally gives a 404) would result in an SSL
error. The thing to do here is to "fix" your network connection, or configure
`gcloud` to use a proxy.
gcloud did the right thing here in refusing to proceed (but should definitely
present a nicer error).
Original comment by z...@google.com
on 5 Feb 2016 at 10:35
Original issue reported on code.google.com by
rbusk...@google.com
on 4 Feb 2016 at 10:27