[chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: berks upload error


Chronological Thread 
  • From: Michael Lindsay < >
  • To:
  • Subject: [chef] Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: berks upload error
  • Date: Tue, 19 May 2015 13:47:01 -0700

4321 is closed to the world (but I can telnet to localhost over it) on that instance and everything is still working like a charm.  The only publicly available ports are 80,443 & 9683.  Thanks for the info!

On Tue, May 19, 2015 at 11:17 AM, Daniel DeLeo < " target="_blank"> > wrote:


On Monday, May 18, 2015 at 12:57 PM, Michael Lindsay wrote:

> Found and fixed!
>
> I'd limited my security group to only accept inbound from office IP for ports 80,443 and 9683 from our office IP adddress. Opening it up to all IP addresses has resolved the problem. Would like to tighten this up at some point (should I add it's own internal ip address? 127.0.0.1/32 (http://127.0.0.1/32)?)
>
> Thanks helping out Stephan and Daniel!
>
> - Michael
You can see the active settings for the Chef Server in /etc/opscode/chef-server-running.json. On my system, bookshelf is configured for 127.0.0.1, port 4321. If that is blocked, the server won’t work. But you shouldn’t need to open up that port to the world.

--
Daniel DeLeo







Archive powered by MHonArc 2.6.16.

§