similar to: Unable to connect to PuppetLabs repository

Hello list, I try to install puppet agent on Debian Lenny. I got following error. Seems the repo is broken : ----------------------------------------------------------------------------------------------------------------------------------- node001:~# wget http://apt.puppetlabs.com/puppetlabs-release-lenny.deb --2012-10-12 02:12:12-- http://apt.puppetlabs.com/puppetlabs-release-lenny.deb

Hello tincers, I run a small tinc mesh using version 1.1pre10 on mostly linux (debian) hosts. In the past, I was able to successfully join my windows machine to the tinc network, when I was running an earlier version of tinc (throughout the mesh). However, with 1.1pre10, I have had no success. Is this a known error, a misconfiguration on my part, or some other issue? I currently have no tinc-up

I discovered that IPv6 is sort of working when I got an email rejection from Comcast for not having an IPv6 PTR record. I discovered I could telnet to port 25 on their MX server over IPv6! I then found I could tracroute6 to them, but I couldn't to my Linode VPS in Fremont. It gets to the data center and stops. Going the other way, my Linode can traceroute6 almost to my AT&T-hosted

I use dovecot on several servers. One of them uses a self-signed cert, it's just me. It worked fine until yesterday when I upgraded my desktop (NOT the server) to CentOS 7.4 Now thunderbird complains when it starts up, and won't let me confirm the security exception. On the server the following error occurs in the log: Sep 25 20:17:49 librelamp dovecot: imap-login: Disconnected (no

All, There are now development package repos located at yum.puppetlabs.com and apt.puppetlabs.com. Moving forward, these repos will contain Release Candidate packages of Puppet, Facter, Puppet Dashboard, MCollective and Hiera, including the soon to be released RCs of Puppet 3.0 and its dependencies, Facter 2.0 and Hiera 1.0. Packages are available to easily add these repos to yum and apt

Hello Everybody, I am trying to install puppet on Red Hat Enterprise Linux Server release 5.8 Beta (Tikanga) I have installed the following rpms sudo rpm -ivh http://yum.puppetlabs.com/el/5/products/i386/puppetlabs-release-5-6.noarch.rpm I am getting the following error when I am trying to install puppet server sudo yum install puppet-server puppet-3.0.1-1.el5.noarch

I'm not running any A/V software, and the same version of dovecot on servers with CA signed certs (komodo) - the client connects to them just fine. On 09/25/2017 01:40 PM, Tony wrote: > It does look like a client issue. Do you also have some kind of AV > running? There are some AV software that can sometimes interfere with > mail sessions. See if you might be running into a similar

I have about 15 nodes running 1.1pre15 connected and running quite well. I don't remember why I installed 1.1preX originally. Possibly because I added a router with custom firmware to the network (Tomato Shibby firmware for my ASUS router) which included 1.1pre14. Now I'm trying to add an Openwrt device and it includes 1.0.33 only. This will replace the Tomato Shibby device with

With the current Thunderbird I can not connect to one of my IMAP servers that uses a self-signed cert. Virtually identical IMAP servers that use CA signed certs work I was a bit out of date when I updated to 7.4 and was running Thunderbird 45.6.x and it worked. When I connected from evolution (which I do not like) it worked. When I connected with my laptop still running 45.6.x it works. so

Hi All, Is there a ubuntu repository managed by puppetlabs? I am using lucid and latest puppet package it offers is 0.25.4. I could of course just download source, or a deb from debian or newer ubuntu, or get it using gem. But would be nice if there is a PPA available for lucid, cuz it would work nicely with routine upgrade. puppetdashboard worked nicely with the puppet labs ppa deb

Hello Micheal, this reminds me of something, that I experienced in the past. Why would the server! complain "Unknown CA"? To test inspect the communication with wireshark and look if the client sends a cert; or: $ echo "a001 LOGOUT" | openssl s_client -msg -connect your.server:993 and grep for "CertificateRequest". Do you have a certificate configured in your

On 09/27/2017 11:14 PM, Phil Perry wrote: > On 28/09/17 04:19, Alice Wonder wrote: >> With the current Thunderbird I can not connect to one of my IMAP >> servers that uses a self-signed cert. Virtually identical IMAP servers >> that use CA signed certs work >> >> I was a bit out of date when I updated to 7.4 and was running >> Thunderbird 45.6.x and it

On 28/09/17 04:19, Alice Wonder wrote: > With the current Thunderbird I can not connect to one of my IMAP servers > that uses a self-signed cert. Virtually identical IMAP servers that use > CA signed certs work > > I was a bit out of date when I updated to 7.4 and was running > Thunderbird 45.6.x and it worked. > > When I connected from evolution (which I do not like)

It does look like a client issue. Do you also have some kind of AV running? There are some AV software that can sometimes interfere with mail sessions. See if you might be running into a similar situation: https://support.mozilla.org/en-US/questions/1066126 Cheers, -- TC On 9/25/17 1:27 PM, Michael A. Peters wrote: > I use dovecot on several servers. One of them uses a self-signed cert, >

Definitely client issue, connecting via evolution works just fine. So I suppose it is off the the thunderbird list. I like thunderbird better. Only plugin I use is dkim validator and when I started thunderbird w/o extensions - still had same issue. But I think it is definitely not a dovecot problem. On 09/25/2017 01:49 PM, Michael A. Peters wrote: > I'm not running any A/V software,

No, no certificate in thunderbird. Work fine when running CentOS 7.3, laptop that still runs 7.3 works fine. I'm going to attempt building the CentOS 7.3 thundirbird src.rpm in 7.4 and see if that fixes it, and if it does, file a bug report with rhel. On 09/26/2017 01:17 AM, Peter Chiochetti wrote: > Hello Micheal, > > this reminds me of something, that I experienced in the past.

I''m attempting to install puppet using the recommended yum method described on the puppetlabs web page: http://docs.puppetlabs.com/guides/installation.html According to http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html#for-red-hat-enterprise-linux-and-derivatives you should execute this: sudo rpm -ivh

I have installed puppet from puppet-labs yum repository on OEL familiy of Red Hat Enterprise Linux Server release 5.9 (Tikanga) ---------------------------------------------------------------------------- [root@oel-puppet-master modules]# yum list facter Loaded plugins: rhnplugin, security This system is not registered with ULN. You can use up2date --register to register. ULN support will be

Last Friday, with a minimum of hiccups, we moved to using freight (http://www.github.com/rcrowley/freight) to handle our repository at apt.puppetlabs.com. One consequence of this move is that the debian repository links will need to be updated. They should be changed to the following: deb http://apt.puppetlabs.com/ $dist main and deb-src http://apt.puppetlabs.com/ $dist main There are symlinks

Hi everyone, I''m going to try announcing new versions of Modules I''m working on as I release them to the Forge. puppet-users and mcollective-users seems like the best place, but please let me know if you have other preferences. I''ve added a small change to the mcollective module we''ve recently released [1]. This change ensures all of the resources managed by