Hi,
since puppet should be used for more clients here, I moved from the 
puppetmaster daemon to a passenger setup (as described on various websites)

Problem is that I am facing the following errors while accessing the REST 
API: (possibly this will hit me with normal clients, too..)
403 You don't have permission to access 
/production/certificate_statuses/no_key on this server.

What I checked up to now:
Puppet CA has the same ownerships as *config.ru* of the Rack Server, 
 "puppet:puppet". So Passenger runs that stuff as the puppet user.

changing config.ru to root for testing made no difference.

Apache Logs only gave me the 403 above, even with extended logging.

Any Idea what this could be or how I can get better debug information what 
passenger does not like here ? ( PassengerLog is currently pointing to the 
webserver logs, but does not tell me anything...)


thanks & best regards,
Björn



-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/3dc7dac0-e0cc-41dc-a3ef-f5282253d7c6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to