Is the opscode server down? I’m doing a bootstrap using the default bootstrap template for chef-client v12.3.0 and I get this.
Connecting to www.opscode.com|184.106.28.91|:443… failed: Connection refused.
Chris
It’s working for me, but I’m getting a different IP from the DNS round robin (184.106.28.82). I’ve forwarded your question to the operations team.
--
Daniel DeLeo
On Thursday, August 27, 2015 at 12:52 PM, Fouts, Chris wrote:
Is the opscode server down? I’m doing a bootstrap using the default bootstrap template for chef-client v12.3.0 and I get this.
Connecting to www.opscode.com (http://www.opscode.com)|184.106.28.91|:443... failed: Connection refused.
Chris
Also working for us using the IP directly:
$ curl -k -v -H 'Host: www.opscode.com (http://www.opscode.com/)' https://184.106.28.91/
- Hostname was NOT found in DNS cache
- Trying 184.106.28.91...
- Connected to 184.106.28.91 (184.106.28.91 (tel:(184.106.28.91)) port 443 (#0)
- TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- Server certificate: *.opscode.com (http://opscode.com/)
- Server certificate: DigiCert SHA2 Secure Server CA
- Server certificate: DigiCert Global Root CA
GET / HTTP/1.1
User-Agent: curl/7.37.1
Accept: /
Host: www.opscode.com (http://www.opscode.com/)
< HTTP/1.1 301 Moved Permanently
- Server ngx_openresty is not blacklisted
< Server: ngx_openresty
< Date: Thu, 27 Aug 2015 20:19:36 GMT
< Content-Type: text/html
< Content-Length: 178
< Connection: keep-alive
< Location: https://www.chef.io/
<
301 Moved Permanently
nginx * Connection #0 to host 184.106.28.91 left intact
--
Daniel DeLeo
On Thursday, August 27, 2015 at 1:20 PM, Daniel DeLeo wrote:
It’s working for me, but I’m getting a different IP from the DNS round robin (184.106.28.82). I’ve forwarded your question to the operations team.
--
Daniel DeLeoOn Thursday, August 27, 2015 at 12:52 PM, Fouts, Chris wrote:
Is the opscode server down? I’m doing a bootstrap using the default bootstrap template for chef-client v12.3.0 and I get this.
Connecting to www.opscode.com (http://www.opscode.com)|184.106.28.91|:443... failed: Connection refused.
Chris
It's working now. We must've had a network glitch internally.
Chris
-----Original Message-----
From: Daniel DeLeo [mailto:ddeleo@kallistec.com] On Behalf Of Daniel DeLeo
Sent: Thursday, August 27, 2015 4:21 PM
To: chef@lists.opscode.com
Subject: [chef] Re: knife bootstrap failing due to failed connection to opscode server?
Also working for us using the IP directly:
$ curl -k -v -H 'Host: www.opscode.com (http://www.opscode.com/)' https://184.106.28.91/
- Hostname was NOT found in DNS cache
- Trying 184.106.28.91...
- Connected to 184.106.28.91 (184.106.28.91 (tel:(184.106.28.91)) port 443 (#0)
- TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- Server certificate: *.opscode.com (http://opscode.com/)
- Server certificate: DigiCert SHA2 Secure Server CA
- Server certificate: DigiCert Global Root CA
GET / HTTP/1.1
User-Agent: curl/7.37.1
Accept: /
Host: www.opscode.com (http://www.opscode.com/)
< HTTP/1.1 301 Moved Permanently
- Server ngx_openresty is not blacklisted < Server: ngx_openresty < Date: Thu, 27 Aug 2015 20:19:36 GMT < Content-Type: text/html < Content-Length: 178 < Connection: keep-alive < Location: https://www.chef.io/ <
301 Moved Permanently
nginx * Connection #0 to host 184.106.28.91 left intact
--
Daniel DeLeo
On Thursday, August 27, 2015 at 1:20 PM, Daniel DeLeo wrote:
It’s working for me, but I’m getting a different IP from the DNS round robin (184.106.28.82). I’ve forwarded your question to the operations team.
--
Daniel DeLeoOn Thursday, August 27, 2015 at 12:52 PM, Fouts, Chris wrote:
Is the opscode server down? I’m doing a bootstrap using the default bootstrap template for chef-client v12.3.0 and I get this.
Connecting to www.opscode.com (http://www.opscode.com)|184.106.28.91|:443... failed: Connection refused.
Chris
This occasionally happens to me, but retrying usually works.
On Thu, Aug 27, 2015 at 1:36 PM, Fouts, Chris Chris.Fouts@sensus.com
wrote:
It's working now. We must've had a network glitch internally.
Chris
-----Original Message-----
From: Daniel DeLeo [mailto:ddeleo@kallistec.com] On Behalf Of Daniel DeLeo
Sent: Thursday, August 27, 2015 4:21 PM
To: chef@lists.opscode.com
Subject: [chef] Re: knife bootstrap failing due to failed connection to
opscode server?Also working for us using the IP directly:
$ curl -k -v -H 'Host: www.opscode.com (http://www.opscode.com/)'
https://184.106.28.91/
- Hostname was NOT found in DNS cache
- Trying 184.106.28.91...
- Connected to 184.106.28.91 (184.106.28.91 (tel:(184.106.28.91)) port 443
(#0)- TLS 1.2 connection using TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
- Server certificate: *.opscode.com (http://opscode.com/)
- Server certificate: DigiCert SHA2 Secure Server CA
- Server certificate: DigiCert Global Root CA
GET / HTTP/1.1
User-Agent: curl/7.37.1
Accept: /
Host: www.opscode.com (http://www.opscode.com/)< HTTP/1.1 301 Moved Permanently
301 Moved Permanently
- Server ngx_openresty is not blacklisted < Server: ngx_openresty < Date:
Thu, 27 Aug 2015 20:19:36 GMT < Content-Type: text/html < Content-Length:
178 < Connection: keep-alive < Location: https://www.chef.io/ <301 Moved Permanently
nginx * Connection #0 to host 184.106.28.91 left intact--
Daniel DeLeoOn Thursday, August 27, 2015 at 1:20 PM, Daniel DeLeo wrote:
It’s working for me, but I’m getting a different IP from the DNS round
robin (184.106.28.82). I’ve forwarded your question to the operations team.--
Daniel DeLeoOn Thursday, August 27, 2015 at 12:52 PM, Fouts, Chris wrote:
Is the opscode server down? I’m doing a bootstrap using the default
bootstrap template for chef-client v12.3.0 and I get this.Connecting to www.opscode.com (http://www.opscode.com)|184.106.28.91|:443...
failed: Connection refused.Chris
--
Yoshi Spendiff
Ops Engineer
Indochino
Mobile: +1 778 952 2025
Email: yoshi.spendiff@indochino.com