Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+change\s+of\s+hostname\s+leads\s+to\s+TLS\s+failure\s*$/: 7 ]

Total 7 documents matching your query.

1. Re: [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Dan Langille <dan AT langille DOT org>
Date: Sun, 1 Feb 2015 10:41:40 -0500
On Jan 31, 2015, at 9:27 PM, Tim Dunphy <bluethundr AT gmail DOT com> wrote: Hey all, I'd like to change the hostname of one of my servers that uses bacula. So I generated some new certs after updati
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-02/msg00000.html (19,178 bytes)

2. Re: [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Tim Dunphy <bluethundr AT gmail DOT com>
Date: Sun, 1 Feb 2015 11:00:50 -0500
I don't see web1.jokefire.com mentioned anywhere until this error.  Why is that? Ok you caught me. Whoops! I was trying to obscure the real name of the domain. That is why.   On Sun, Feb 1, 2015 at 1
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-02/msg00002.html (19,629 bytes)

3. Re: [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Dan Langille <dan AT langille DOT org>
Date: Sun, 1 Feb 2015 11:04:34 -0500
Make sure the Address field in the Client resource in bacula-dir.conf is web1.jokefire.com Make sure the cert is for web1.jokefire.com If not, that may be the problem. Dan Langille http://langille.o
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-02/msg00004.html (19,427 bytes)

4. Re: [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Josh Fisher <jfisher AT pvct DOT com>
Date: Mon, 02 Feb 2015 13:01:18 -0500
The commonName (CN) of the certificate needs to match the hostname. Does the commonName field (CN) of the certificate match the hostname? -- Dive into the World of Parallel Programming. The Go Parall
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-02/msg00027.html (12,585 bytes)

5. Re: [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Kern Sibbald <kern AT sibbald DOT com>
Date: Tue, 03 Feb 2015 09:56:54 +0100
If I am not mistaken in version 7.0.x I implemented wild-card hostnames (a single asterisk. e.g. *.mydomain.com), but it is not well tested. This could resolve the problem, but it also permits anyone
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-02/msg00029.html (14,072 bytes)

6. Re: [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Ana Emília M. Arruda <emiliaarruda AT gmail DOT com>
Date: Tue, 3 Feb 2015 23:14:16 -0300
Hey Tim! Have you changed the certificates for this client (web1.mydomain.com) in the client's section in bacula-dir.conf? Is the web1.mydomain.com the director and a client too? If not, you don't ne
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-02/msg00030.html (18,716 bytes)

7. [Bacula-users] change of hostname leads to TLS failure (score: 1)
Author: Tim Dunphy <bluethundr AT gmail DOT com>
Date: Sat, 31 Jan 2015 21:27:31 -0500
Hey all,   I'd like to change the hostname of one of my servers that uses bacula.   So I generated some new certs after updating the hostname in /etc/hosts: [root@web1:/etc/bacula] #ls -l /etc/pki/tl
/usr/local/webapp/mharc-adsm.org/html/Bacula-users/2015-01/msg00200.html (15,403 bytes)


This search system is powered by Namazu