[Puppet Users] Re: puppetmaster behind NAT

2009-07-01 Thread Peter Meier
Hi >> the puppet masters cert and CA needs to contain the public FQDN as well. >> use certnames (see ConfigurationReference [1]) to include both domains, >> local and public. This will mean that you need to regenerate the certs, >> as well to resign all clients. > > > Thanks again, it worked ju

[Puppet Users] Re: puppetmaster behind NAT

2009-06-30 Thread Pavel Shevaev
> the puppet masters cert and CA needs to contain the public FQDN as well. > use certnames (see ConfigurationReference [1]) to include both domains, > local and public. This will mean that you need to regenerate the certs, > as well to resign all clients. Thanks again, it worked just fine. BTW,

[Puppet Users] Re: puppetmaster behind NAT

2009-06-30 Thread Pavel Shevaev
> I assume that you use a different FQDN internal and external, right? Exactly > So then: > > the puppet masters cert and CA needs to contain the public FQDN as well. > use certnames (see ConfigurationReference [1]) to include both domains, > local and public. This will mean that you need to reg

[Puppet Users] Re: puppetmaster behind NAT

2009-06-30 Thread Peter Meier
Hi > Jun 30 16:20:02 puppetd[22640]: Could not retrieve catalog: > Certificates were not trusted: hostname was not match with the server > certificate > > I guess it happens because puppetd clients are expecting the > puppetmaster to have FQDN name of the router which is not the case... > Is th