Yes. The CN of the certificate needs to match what you put as the
Address for the client configuration. i.e. Client { Name = server-fd Address = server.domain FDPort = 9102 Catalog = Catalog Password = Password AutoPrune = yes TLS Enable = yes TLS Require = yes TLS CA Certificate File = /bacula/CA.cachain.pem TLS Certificate = /bacula/DIR_SERVER_CERT.pem TLS Key = /bacula/DIR_SERVER_KEY.pem } ~Jet John Drescher wrote: On Thu, Jul 30, 2009 at 11:03 AM, Siyoucef Arslan<siyoucef.ars...@yahoo.fr> wrote:hello I add a new external client, but I always have the same problem; is that a person who has already successfully e TLS connect? arslanThe following appears to be the problem: 29-jui 15:36 bconsole JobId 0: Erreur fatale : bnet.c:307 TLS host certificate verification failed. Host name "127.0.0.1" did not match presented certificate However since I do not use TLS I am not sure exactly what steps to take to fix this. Perhaps replacing the ipaddress with a host name or FQDN that matched your certificate generation. I am not sure. |
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users