© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Yes, the node has full access to the internet:
By explicitly executing: sudo pollinate
I get:
Feb 26 14:35:23 stream1 pollinate[26489]: client sent challenge to [https:/
Feb 26 14:35:24 stream1 pollinate[26513]: ERROR: Network communication failed [60]\n14:
% Total % Received % Xferd Average Speed Time Time Time Current
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 014:35:24.299301 * Trying 91.189.94.50...
14:35:24.324169 * Connected to entropy.ubuntu.com (91.189.94.50) port 443 (#0)
14:35:24.325201 * successfully set certificate verify locations:
14:35:24.325254 * CAfile: /etc/pollinate/
CApath: /dev/null
14:35:24.325410 * SSLv3, TLS handshake, Client hello (1):
14:35:24.325460 } [data not shown]
14:35:24.350528 * SSLv3, TLS handshake, Server hello (2):
14:35:24.350592 { [data not shown]
14:35:24.363801 * SSLv3, TLS handshake, CERT (11):
14:35:24.363852 { [data not shown]
14:35:24.364434 * SSLv3, TLS alert, Server hello (2):
14:35:24.364486 } [data not shown]
14:35:24.364643 * SSL certificate problem: self signed certificate in certificate chain
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
14:35:24.364884 * Closing connection 0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: http://
curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.