Hi Andrew, sorry I wasn't clear -- The config.ru is probably fine, the
problem is more likely in the Apache configuration (usually in
/etc/httpd/conf.d/) that sets up the two virtual hosts (One for the
puppetmaster and the other for Dashboard). There might be an overlapping
virtualhost
This is the config.ru file that I have inside the folder
/usr/share/puppet-dashboard :
# a config.ru, for use with every rack-compatible webserver.
# SSL needs to be handled outside this, though.
# if puppet is not in your RUBYLIB:
# $LOAD_PATH.unshift('/opt/puppet/lib')
$0 = master
# if you
Hi andrew, that error is one that comes from the puppet master process
itself when you connect to it with a regular HTTP client. So it looks like
your apache virtualhost setup is pointing connections to that port/host at
the puppetmaster config.ru, not dashboard. Does that help track down the