[Puppet Users] Re: Error sending reports to dashboard

I wanted to configure the puppet dashboard to require authentication of client certs and had to modify the previous script to get it to send the client certificate. I also adjusted it to use the puppet CA cert to verify the remote server as well. Simple changes, but providing it in case anyone

[Puppet Users] Re: Error sending reports to dashboard

Julien, Thanks, this solved the issue for me. We had the puppet dashboard running on a separate host to the Puppet masters. The puppet masters were trying to send the reports to the Dashboard using HTTP when the dashboard comes configured for HTTPS. So I copied the /opt/puppet/lib/ruby/site_rub

[Puppet Users] Re: Error sending reports to dashboard

Hi, In your puppet.conf, change : [master] reports = log, store, http*s* reporturl = https://puppet-test.uis.example.com:443/reports/upload Then add in your reports folder (under debian with puppetlabs packets) ; /usr/lib/ruby/1.8/puppet/

Re: [Puppet Users] Re: Error sending reports to dashboard

Hi, I'm also having this issue running puppet-2.7.16 & puppet-dashboard-1.2.9 on CentOS 6.2. Has there been any solution to this yet besides running redundant vhosts? In either case, can you please post your apache vhost configuration files? On Monday, April 11, 2011 12:55:10 PM UTC-4, Mohamed

Re: [Puppet Users] Re: Error sending reports to dashboard

My point exactly for now, though there are reasons to send reports over HTTPS that I mentioned in my response. On Apr 14, 2011, at 7:19 PM, Mohamed Lrhazi wrote: > Sure. but if you already configured access to puppetmaster on HTTPS, > it would be nice to use it, instead of adding and maintaining

Re: [Puppet Users] Re: Error sending reports to dashboard

On Apr 14, 2011, at 3:54 PM, Cody Robertson wrote: > Although I don't know the answer I'm curious as to why you're worried about > using HTTPS when you're sending the reports locally? There is no need to > encrypt the ports if you're just sending them to the same machine / localhost. In my cas

Re: [Puppet Users] Re: Error sending reports to dashboard

Sure. but if you already configured access to puppetmaster on HTTPS, it would be nice to use it, instead of adding and maintaining another setup for HTTP access. On Thu, Apr 14, 2011 at 6:54 PM, Cody Robertson wrote: > Although I don't know the answer I'm curious as to why you're worried about >

[Puppet Users] Re: Error sending reports to dashboard

Although I don't know the answer I'm curious as to why you're worried about using HTTPS when you're sending the reports locally? There is no need to encrypt the ports if you're just sending them to the same machine / localhost. -- You received this message because you are subscribed to the Goo

Re: [Puppet Users] Re: Error sending reports to dashboard

On 04/11/2011 06:55 PM, Mohamed Lrhazi wrote: > I did not find any reference I just added a second apache virtual > server to do http on port 80. > > On Mon, Apr 11, 2011 at 12:14 PM, Patrick wrote: >> Bump. Anyone know the answer? Can puppet use https to post reports? I'm >> having trou

Re: [Puppet Users] Re: Error sending reports to dashboard

I did not find any reference I just added a second apache virtual server to do http on port 80. On Mon, Apr 11, 2011 at 12:14 PM, Patrick wrote: > Bump.  Anyone know the answer?  Can puppet use https to post reports?  I'm > having trouble sending reports using https too, although I haven't

Re: [Puppet Users] Re: Error sending reports to dashboard

Bump. Anyone know the answer? Can puppet use https to post reports? I'm having trouble sending reports using https too, although I haven't yet found anything useful in the logs. On Mar 21, 2011, at 9:41 PM, Mohamed Lrhazi wrote: > I enabled debug log level in apache virtual and it seems like

[Puppet Users] Re: Error sending reports to dashboard

I enabled debug log level in apache virtual and it seems like puppetmaster is trying to speak http, instead of https. Is https not supported for posting reports? [Tue Mar 22 00:39:43 2011] [debug] ssl_engine_io.c(1819): OpenSSL: read 11/11 bytes from BIO#2b225d284100 [mem: 2b225d2f9650] (BIO dump

[Puppet Users] Re: Error sending reports to dashboard

If I run the dash-board directly, with built-in web-server, on default port, and remove the reporturl , reports are posted successfully! Any idea what I am missing for a behind apache/Phusion setup? Thanks a lot. Mohamed. On Mon, Mar 21, 2011 at 7:12 PM, Mohamed Lrhazi wrote: > [master] >  repo