Reporting fails

Hello List,

I´d like to start using foreman with reports only, to have a nice report
gui :slight_smile:

I´ve installed foreman 1.1 (on RHEL 6.4), this is my settings.yaml:
:unattended: false
:login: true
:require_ssl: false
:locations_enabled: false
:organizations_enabled: false
and then added foreman.rb to my puppetmaster, reports=foreman, report=true
on my agent and so on…

puppet agent on my node runs fine, but foreman gets no report because this
error message /var/log/foreman/production.log

Started POST "/reports/create?format=yml" for 4.128.100.64 at Thu May 16
15:56:09 +0200 2013
Processing by ReportsController#create as YML
Parameters: {"report"=>"[FILTERED]"}
No smart proxy server found on ["ippm01.dc.hn.de.kaufland"]
Redirected to http://ippfm01.dc.hn.de.kaufland:3000/users/login
Completed 403 Forbidden in 34ms

so is the deployment of at least one smart proxy server mandatory
even if´d only like to send puppet reports to foreman?

thanks

··· , Stefan

It's only mandatory if you want to be secure - YAML uploads have know
exploits in Rails.

However, since you've already turned SSL off, you may as well turn this off
too - go to More -> Settings in the UI and set
:require_registered_puppetmasters to false.

HTH,
Greg

··· On 16 May 2013 15:46, Stefan Wiederoder wrote:

Hello List,

so is the deployment of at least one smart proxy server mandatory
even if´d only like to send puppet reports to foreman?

Hello Greg,

that´s it - now I´m receiving reports - thanks a lot!

Great! I'd be out-of-line if I didn't suggest that once you're done
testing, you do add a smart-proxy and switch SSL/registration back on :slight_smile:

In the next version of Foreman there's a also a way to whitelist certain
hostnames without needing an smart-proxy, which might be useful to you.

Greg

··· On 17 May 2013 15:34, Stefan Wiederoder wrote:

Hello Greg,

that´s it - now I´m receiving reports - thanks a lot!