Did something change in Foreman 1.12.3 then? I did exactly as you showed, but it broke Puppet.
On the verbose output from Foreman I get the error: [ERROR 2016-09-30 19:20:14 verbose] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[*myhostfqdn*]: Could not evaluate: Exception SSL_connect returned=1 errno=0 state=error: certificate verify failed in get request to: https://dlistmrfpup02.cbs.ad.cbs.net/api/v2/smart_proxies?search=name=%22 *myhostfqdn*%22 On the agent I am getting: Warning: Unable to fetch my node definition, but the agent run will continue: Warning: Find /development/node/*myagent.fqdn*?transaction_uuid=171b325c-72e8-49c1-9a7a-6479fb4c44... resulted in 404 with the message: {"message": "Not Found: Could not find node *myagent.fqdn*","issue_kind":"RESOURCE_NOT_FOUND"} It was working before I added my SSL certs for the host. The webserver works fine with the https:// access with the certificate being valid, but Puppet is not able to use the webserver connection to do anything with facts. I have tried your techniques and all listed above by the OP. Is it really this hard to put a valid SSL certificate on a Foreman server running Puppet? I figured I am really missing something simple. -- 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.
