Hello
Perhaps I can tackle this a different way. As mentioned in my original post
I used the Ubuntu 14 Puppet DB package on Ubuntu 16 because Ubuntu no
longer provided a PuppetDB package for Xenial. It's Java so as long as the
schema is unchanged it should still work, right? So has the schema c
> On 19 Jul 2018, at 21:19, Henrik Lindberg wrote:
>
>> On 2018-07-19 17:15, Helmut Schneider wrote:
>> Hi,
>> ---
>> profiles:
>> vpn:
>> openvpn:
>> defaults:
>> client:
>> dev: 'tun'
>> proto: 'udp'
>> resolv-retry:
If you're reaching expiry you might consider this thing, it worked for me to
refresh the CA cert:
https://forge.puppet.com/puppetlabs/certregen
(NB, check all your puppetserver/puppetmaster hosts for stray puppet/ssl/ca
directories, having extra ones around can cause a bit of pain. Make sure yo
On 2018-07-19 17:15, Helmut Schneider wrote:
Hi,
---
profiles:
vpn:
openvpn:
defaults:
client:
dev: 'tun'
proto: 'udp'
resolv-retry: 'infinite'
nobind:
user: 'nobody'
I did, by building a new server. That said, I'd try this advice before
starting over:
https://puppet.com/docs/puppet/5.5/ssl_regenerate_certificates.html
For us it was also a change to move from a monolithic, everything on one
server architecture to something a bit more distributed.
On Thu, Jul 1
Were you able to resolve this issue? I am now getting the same problem
Thanks
Scott
--
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 puppet-users+unsubscr..
Hi,
---
profiles:
vpn:
openvpn:
defaults:
client:
dev: 'tun'
proto: 'udp'
resolv-retry: 'infinite'
nobind:
user: 'nobody'
group: 'nogroup'
persist-key:
