Hi Rohit, Is the hostname from `/CN=our.puppet.domain` showing up in your puppetserver's certificate? You can verify that with `puppet cert list --all` on the puppetserver container. This looks like a DNS issue.
On Thursday, October 18, 2018 at 11:41:16 AM UTC-7, Rohit wrote: > > Hello, we currently have a puppet docker container setup and are > experiencing certificate issues. Basically, in our docker setup (on our > main server) I had generated and signed new certificates, but the puppet_db > container keeps restarting. Here are logs from the puppet_db container: > > ‘Error: Could not retrieve catalog from remote server: SSL_connect > returned=1 errno=0 state=error: certificate verify failed: [unable to get > local issuer certificate for /CN=our.puppet.domain] > Error: Could not retrieve catalog; skipping run > Error: Could not send report: SSL_connect returned=1 errno=0 > state=error: certificate verify failed: [unable to get local issuer > certificate for /CN=our.puppet.domain]’ > > I have tried series of steps to solve this problem as it looks like Puppet > is not functioning correctly as our servers are not properly listening to > the host server. Any idea what I can do to solve this problem? For > reference, we are running Puppet_DB version 4.2 and Puppet Server version > 2.7.2, all of which is set up on a docker container environment on one > server. > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/1a315e30-fd7f-4da8-ba52-52da56756311%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
