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 need to change the first part
of the bacula-fd.conf because there are the director's certificate and
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 in the domain
to access the server.
Best regards,
Kern
On 02.02.2015 19:01, Josh Fisher wrote:
The commonName (CN) of the certificate needs to match the hostname.
On 1/31/2015 9:27 PM, Tim Dunphy 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 updating the hostname in /etc/hosts:
>
> [root@web1:/etc/bacu
>
> On Feb 1, 2015, at 11:00 AM, Tim Dunphy wrote:
>
> 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.
Make sure the Address field in the Client resource in
>
> 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 10:41 AM, Dan Langille wrote:
>
> On Jan 31, 2015, at 9:27 PM, Tim Dunphy wrote:
>
> Hey al
> On Jan 31, 2015, at 9:27 PM, Tim Dunphy 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 updating the hostname in /etc/hosts:
>
> [root@web1:/etc/bacula] #ls -l /etc/pki/tls/* | grep web1
> -r
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/tls/* | grep web1
-r 1 root root 1956 Jan 31 20:34 web1.mydomain.com.crt
-r 1
