OK, so this is a straight line version of how I debugged the issue. There
were a couple more dead ends than described here.
The first thing to notice is the error. I was getting: "certificate verify
failed: [self signed certificate for
/C=--/ST=SomeState/L=SomeCity/O=SomeOrganization/OU=SomeOr
It took a bit of digging - but I did workout what the issue was. I'll give
the solution first and then an overview of how I diagnosed the issue It
may be useful to others with SSL issues.
I was running Puppet on a Red Hat server. By default Red Hat installs an
SSL configuration in /etc/httpd
Hi everybody
I've been running puppet under Apache/Passenger for some time. I restarted
Apache this morning I'm getting the following error
---
[root@ecm-rhl-032 ~]# puppet agent --test
Warning: Unable to fetch my node definition, but the agent run will
continue:
Warning: SSL_connect returned=
Hi Spencer
That's fixed the ssl issue. Not sure where I got the /etc/puppet/ssl...
from.
I've got some "access denied" issues now. Trace them down another day
Thanks for the help
Tom
On Sunday, 23 March 2014 02:16:12 UTC+8, Tom Hallam wrote:
>
> Ahh, those line
our apache vhost pointing to specific
> ssl certs. Can you verify that all these paths are correct?
>
> Specifically the lines beginning with SSL in
> http://docs.puppetlabs.com/guides/passenger.html#create-and-enable-the-puppet-master-vhost
>
>
> On Sat, Mar 22, 2014 at 7:
Hi
Just tried
openssl s_client -connect puppet...:8140 -showcerts /tmp/file
To get the certificates from each server and they are not the same. I've
checked /etc/puppet/ssl and the Pasenger configuration is giving me the
same certificates as are in there. Can't find ones that match WebBrick
Hi All
I've been running Puppet using the build in web server and I'm now moving
to Apache and Passenger. I've completed the installation and started
testing. If I run
puppet agent --test --noop
I get the following error (domain removed)
Warning: Unable to fetch my node definition, but
