> Did you modify your auth.conf? > Look at your auth.conf and put the following lines near the beginning > of the file to ensure that it gets evaluated first: > > path / > auth no > allow * > > If it works, then you can be sure it is some permission or > authorization problem.
I'm having the same issue (definitely auth.conf) but I don't see why it works under webrick. It's only under passenger that it barfs. Is that the expected behaviour? Mine works fine if I "auth no" to all my methods but that sort of defeats the purpose of the security methods. If it is a permission or authorisation problem, what could it be? I have a clean build with new certs; all works as expected when puppetmasterd is run (client connects and is authorised). My auth.conf file currently looks like this - http://pastie.org/1089444 Sven -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.