similar to: err: Could not request certificate: sslv3 alert handshake failure error

I''ve setup a puppet load-balanced solution based on these instructions: http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Scalability I have 4 puppetmaster instances running on my puppet server and an Apache instance running on that server listening on port 8140 and round-robining the requests from puppet clients. This works fine for all my existing client machines. The problem

Hi! I''ve installed puppetmaster 2.7.13 on a server with CentOS 6.2 with a rpm supplied by yum.puppetlabs.com. I''ve setup a apache2 vhost with mod_ssl and passenger. The server is configured to autosign the cert requests. The agent installed on the puppetmaster''s server works fine. I''ve a second agent on a server which can sync with the server too. This

On R 3.2.5, 3.3.2 and devel for Windows, R CMD check --as-cran gives me: Found the following (possibly) invalid URLs: URL: https://www.stat.auckland.ac.nz/~paul/Reports/DisplayList/dl-record.html From: man/capturePlot.Rd Status: Error Message: libcurl error code 35 error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure This is reported both by the

Hi All, I am using "asterisk-11.12.0" version and I am trying to setup secure call (TLS + SRTP) between two extensions and while making a call, I got following error *CLI> == Using SIP RTP CoS mark 5 -- Executing [6004 at from-office:1] Dial("SIP/6003-00000000", "SIP/6004,20") in new stack == Using SIP RTP CoS mark 5 -- Called SIP/6004 SSL certificate

Hi - I read up on this subject quite a bit, and was able to find a few posts on the mailing list, even found a wiki article. Unfortunately it doesn''t quite address what I''m looking to do. From what I understand, Puppet''s client/server authentication system - using SSL - is portable. I believe that I should be able to use the same SSL certificates and keys (and even

Hi i have the running i both sides, client and server sides the puppet 0.25.4 Get this error on server side: puppetmasterd[5363]: Report puppet_dashboard failed: wrong Content-Length format And receive this error on my client side: warning: Value of ''preferred_serialization_format'' (pson) is invalid for report, user default (b64_zlib_yaml) I am getting any reports on my

So set up new node, ran on the client puppetd --server puppetmaster --waitforcert 60 --test on the puppetmaster itself I ran puppetca --list saw the hostname and then ran: puppetca --sign hostname.domain.com and on the puppet node itself I went back and ran puppetd -tv and get the following error: err: Could not retrieve catalog from remote server: certificate verify failed warning: Not

Here we go with puppet 0.25 certificate problems again. I had a system where puppet was running fine. I reinstalled it. Running puppet on the client causes this: "Could not request certificate: Retrieved certificate does not match private key; please remove certificate from server and regenerate it with the current key". Fine... so I run ''puppetca --clean

I get errors like this randomly on some of my puppet clients: puppetd[7303]: (//munin/Config-file[muninnode]/File[/etc/m unin/munin-node.conf]) Failed to retrieve current state of resource: Could not retrieve file metadata for puppet://puppet.hq.eso.org/modules/munin/munin-node.c onf: at /etc/puppet/manifests/site.pp:41 The relevant definition from /etc/puppet/manifests/site.pp is: # Generic

Dear all, I see this error message in my *masterhttp.log* repeatedly: ERROR OpenSSL::SSL::SSLError: SSL_accept returned=1 errno=0 state=SSLv3 > read client certificate A: tlsv1 alert unknown ca > I saw a similar mail in the list but there was no definitive answer to that post. Does anyone know what am I missing here? I do understand what *unknown ca* means but I can''t think

Hello, In the wiki "Using_Mongrel" http://projects.reductivelabs.com/projects/puppet/wiki/Using_Mongrel it proposes a configuration with the option: SSLVerifyClient require But with this option set I am not able to register new clients. When I run a new puppet client, I get the error: warning: peer certificate won''t be verified in this SSL session err: Could not request

Hi list, I am trying to get a puppet certificate on a new client but I get error: err: Could not request certificate: undefined method `closed?'' for nil:NilClass I googled and found that it had something to do with reverse DNS lookup, the client is behind a NAT firewall so I assume a reverse lookup will fail. Can I bypass this somehow? Puppet version on master and client is 0.25.4

Our puppetmaster runs 0.24.8 on Ubuntu 9.10. Our clients are either Ubuntu 9.10 or Ubuntu 8.04. We''ve just brought up our first Ubuntu 10.04 machine. This machine installs puppetd 0.25.4. The Ubuntu 10.04 machine can''t seem to present it''s certificate request properly. In my masterhttp.log, I see [2010-10-20 13:09:06] 174-143-141-55.static.cloud-ips.com - -

I''m having difficulty getting my head around some CA issues My client has: [puppetd] ca_server=puppetca.mydomain.com and puppet resolves to a different machine. when puppet connects, it requests a signature from puppetca.mydomain.combut then on the next pass fails with the following: err: Could not retrieve catalog: Certificates were not trusted: SSL_connect returned=1 errno=0

hello, my webrtc calls ends after ~60seconds with "res_rtp_asterisk.c: DTLS failure occurred on RTP instance '0xb6c02a94' due to reason 'sslv3 alert unexpected message', terminating". any ideas where can be problem? or howto debug this problem? asterisk13.4.0-rc1 + sipml5 latest (chrome,firefox) -- --------------------------------------- Marek Cervenka

Hi , I am new to this puppet. I am implementing a network where my cisco switch will contact the puppet server for getting the configuration. I tried installing open source puppet and was successful in pushing down the configurations. I wanted then to try the same exercise with puppet enterprise 3.1. I installed puppet enterprise in a different server and changed my puppet agent (switch) to

Hi, First of all I''ve googled this subject a lot (several hours) but right now I''m simply stuck. All my 4 DomU fails SSL handshake: > niklas@stats:~$ curl -vI https://graph.facebook.com > * About to connect() to graph.facebook.com port 443 (#0) > * Trying 69.63.181.58... connected > * Connected to graph.facebook.com (69.63.181.58) port 443 (#0) > * successfully

I am banging my head against the wall for recently built hosts that are unable to verify the server''s certs. The usual is not working. on the puppet agent machine: find /var/lib/puppet/ssl -type f -delete on puppet master: puppetca --clean <new_host_cert> on agent: puppetd --server puppet --waitforcert 2 --no-daemonize -d -o on puppet master: puppetca --sign

Hi, I have setup puppet (2.7.5) on 2 different machines on ec2. Puppet master config 1. Ruby - 1.9.3 2. OS - Amazon linux image 3. runs from root user Puppet agent config 1. Ruby - 1.9.3 2. OS - centos 3. runs from root user When i run the agent, it throws an error "unknown ca" (can been seen in tcpdump/server logs) and closes the SSL connection immediately. I tried following things

Hi, I''m using puppet on EC2 to setup my VMs with the following configuration: # puppetd --version 0.25.5 # uname -a Linux hostname.domain 2.6.16-xenU #1 SMP Mon May 28 03:41:49 SAST 2007 i686 i686 i386 GNU/Linux But I keep facing some timeout from puppetd: warning: peer certificate won''t be verified in this SSL session Exiting; failed to retrieve certificate and waitforcert