I suggest changing this via foreman-installer. This ensures that updates won't break your configuration.
foreman-installer -v \ --foreman-foreman-url=puppet.example.com \ --foreman-server-ssl-cert=/etc/pki/tls/certs/puppet.example.com.crt \ --foreman-server-ssl-key=/etc/pki/tls/private/puppet.example.com.key \ --foreman-server-ssl-chain /etc/pki/tls/example.com.root.pem Make sure to include all the intermediate certificates in the root chain. On Wednesday, June 15, 2016 at 11:30:46 PM UTC+2, johny casanova wrote: > > helo, > > I followed the guide in > https://www.theforeman.org/2015/11/foreman-ssl.html and changed the certs > in SSLCertificateFile "/etc/pki/tls/certs/puppet.example.com.crt" > SSLCertificateKeyFile "/etc/pki/tls/private/puppet.example.com.key" but, > after making this change another puppet host cant connect after running > puppet agent -t > > > I get this error: puppetpuppet agent unable to fetch my node definition > error 400 agent unable to fetch my node definition error 400 > -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
