# Knife bootstrap failing due to failed connection to opscode server?

**URL:** <https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843>\
**Category:** Chef Infra (archive)\
**Created:** [August 27, 2015, 7:52pm UTC](https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843 "2015-08-27T19:52:02Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)\
**Post date:** [August 27, 2015, 7:52pm UTC](https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843/1 "2015-08-27T19:52:02Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![kallistec](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/kallistec/32/23_2.png) [@kallistec](https://discourse.chef.io/u/kallistec)\
**Post date:** [August 27, 2015, 8:20pm UTC](https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843/2 "2015-08-27T20:20:04Z")

</div>

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) ([http://www.opscode.com](http://www.opscode.com))|184.106.28.91|:443... failed: Connection refused.
> 
> Chris

---

<div class="post-metadata">

**Author:** ![kallistec](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/kallistec/32/23_2.png) [@kallistec](https://discourse.chef.io/u/kallistec)\
**Post date:** [August 27, 2015, 8:21pm UTC](https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843/3 "2015-08-27T20:21:10Z")

</div>

Also working for us using the IP directly:

$ curl -k -v -H 'Host: [www.opscode.com](http://www.opscode.com) ([http://www.opscode.com/](http://www.opscode.com/))' [https://184.106.28.91/](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/](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://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/](https://www.chef.io/)  
\<

301 Moved Permanently
# 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 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) ([http://www.opscode.com](http://www.opscode.com))|184.106.28.91|:443... failed: Connection refused.
> > 
> > Chris

---

<div class="post-metadata">

**Author:** ![Chris\_F](https://avatars.discourse-cdn.com/v4/letter/c/fbc32d/32.png) [@Chris\_F](https://discourse.chef.io/u/Chris_F)\
**Post date:** [August 27, 2015, 8:36pm UTC](https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843/4 "2015-08-27T20:36:38Z")

</div>

It's working now. We must've had a network glitch internally.

Chris

-----Original Message-----  
From: Daniel DeLeo [[mailto:ddeleo@kallistec.com](mailto:ddeleo@kallistec.com)] On Behalf Of Daniel DeLeo  
Sent: Thursday, August 27, 2015 4:21 PM  
To: [chef@lists.opscode.com](mailto: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) ([http://www.opscode.com/](http://www.opscode.com/))' [https://184.106.28.91/](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/](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://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/](https://www.chef.io/) \< 

301 Moved Permanently 
# 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 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) ([http://www.opscode.com](http://www.opscode.com))|184.106.28.91|:443... failed: Connection refused.
> > 
> > Chris

---

<div class="post-metadata">

**Author:** ![Yoshi\_Spendiff](https://sea2.discourse-cdn.com/flex016/user_avatar/discourse.chef.io/yoshi_spendiff/32/13_2.png) [@Yoshi\_Spendiff](https://discourse.chef.io/u/Yoshi_Spendiff)\
**Post date:** [August 27, 2015, 8:52pm UTC](https://discourse.chef.io/t/knife-bootstrap-failing-due-to-failed-connection-to-opscode-server/6843/5 "2015-08-27T20:52:24Z")

</div>

This occasionally happens to me, but retrying usually works.

On Thu, Aug 27, 2015 at 1:36 PM, Fouts, Chris [Chris.Fouts@sensus.com](mailto: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](mailto:ddeleo@kallistec.com)] On Behalf Of Daniel DeLeo  
> Sent: Thursday, August 27, 2015 4:21 PM  
> To: [chef@lists.opscode.com](mailto: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) ([http://www.opscode.com/](http://www.opscode.com/))'  
> [https://184.106.28.91/](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/](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://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/](https://www.chef.io/) \< 
> 
> 301 Moved Permanently 
> # 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 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) ([http://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](mailto:yoshi.spendiff@indochino.com)