Hey,
It should work, Puppetboard is supposed to just pass in the settings to
pypuppetdb so unless we really screwed up somewhere that shouldn't be the
issue.
Can you show me your settings.py file?
--
Daniele Sluijters
On Saturday, 8 February 2014 23:35:43 UTC+1, Johan De Wit wrote:
Hi,
Hoi Daniele,
/var/www/puppetboard/settings.py
PUPPETDB_HOST = 'puppet.koewacht.net'
PUPPETDB_PORT = 8080
#PUPPETDB_SSL_VERIFY = True
#PUPPETDB_KEY = '/etc/puppetboard/pb_priv.pem'
#PUPPETDB_CERT ='/etc/pupeptboard/pb_pub.pem'
PUPPETDB_TIMEOUT = 20
DEV_LISTEN_HOST = '127.0.0.1'
DEV_LISTEN_PORT =
Daniele,
I should create an alias pupept=puppet :)
I will test this further this evening, but seems logic the typo did it
(well broke it)
On 02/10/2014 03:48 PM, Johan De Wit wrote:
Hoi Daniele,
/var/www/puppetboard/settings.py
PUPPETDB_HOST = 'puppet.koewacht.net'
PUPPETDB_PORT = 8080
Daniele,
It was not the typo. But it seems the ssl_verify=True did the bad thing.
db =
connect(host='puppet.koewacht.net',port='8081',ssl_key='/etc/puppetboard/pb_priv.pem',ssl_cert='/etc/puppetboard/pb_pub.pem',api_version=3,ssl_verify=True,timeout=20)
nodes = db.nodes()
for node in
Hey Johan,
SSL_VERIFY trips up a few people, I need better docs on that.
When you connect to PuppetDB as a client you need to present two things, a
private key and a public key signed by the Certificate Authority that also
signed the server certificate of PuppetDB. This in all likeliness is
