TLS Handshake failed

[Stefan Harbich]

Hello,

i'm getting an error message I can't identify.

...
13-Nov 12:00 bareos-dir JobId 0: Fatal error: Tls handshake failed.
13-Nov 12:00 bareos-dir: ERROR in dird/authenticate_console.cc:353 Unable to authenticate console "*UserAgent*" at client:192.168.20.20:9101.
...
All addresses are specified as FQDNs in the configuration files, not as IP addresses. Or is the IP address returned via DNS and displayed as an error message? I suspect the error occurs during client setup. However, I'm not clear on which connection setup is being discussed here:
- From the Director to the Console
- From the Director to the Client, or vice versa?
How can I find out more details? Where and how do I need to enable debugging? Regards, Stefan Harbich

[Stefan Harbich]

Hello,

i was able to solve the problem. Years ago, I added a Python script, "triggerjob.py," to back up mobile host systems (laptops). These aren't always on the company network. Is there a better solution for this now, since mobile devices also use different IP addresses (Internet/Intranet/VPN)?

Regards, Stefan Harbich

[Jörg Steffens]

On 14.11.25 at 23:01 wrote Stefan Harbich:

> Hello,
> i was able to solve the problem. Years ago, I added a Python script,
> "triggerjob.py," to back up mobile host systems (laptops). These aren't
> always on the company network. Is there a better solution for this now,
> since mobile devices also use different IP addresses (Internet/Intranet/
> VPN)?

not sure, if there is a better solution, but when using Python >= 3.13,
the underlying python-bareos uses TLS-PSK. So you should get rid of the
TLS handshake errors.

Regards,
Jörg

> Regards, Stefan Harbich
>
> Stefan Harbich schrieb am Donnerstag, 13. November 2025 um 12:20:18 UTC+1:
>
> Hello,
> i'm getting an error message I can't identify.
>
> ...
> 13-Nov 12:00 bareos-dir JobId 0: Fatal error: Tls handshake failed.
> 13-Nov 12:00 bareos-dir: ERROR in dird/authenticate_console.cc:353
> Unable to authenticate console "*UserAgent*" at

> client:192.168.20.20:9101 <http://192.168.20.20:9101>.

> ...
> All addresses are specified as FQDNs in the configuration files, not
> as IP addresses. Or is the IP address returned via DNS and displayed
> as an error message? I suspect the error occurs during client setup.
> However, I'm not clear on which connection setup is being discussed
> here:
> - From the Director to the Console
> - From the Director to the Client, or vice versa?
> How can I find out more details? Where and how do I need to enable
> debugging? Regards, Stefan Harbich
>

> --
> You received this message because you are subscribed to the Google
> Groups "bareos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to bareos-users...@googlegroups.com <mailto:bareos-
> users+un...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/bareos-
> users/0460f338-2c2e-47a3-8f62-37b559139ab1n%40googlegroups.com <https://
> groups.google.com/d/msgid/bareos-
> users/0460f338-2c2e-47a3-8f62-37b559139ab1n%40googlegroups.com?
> utm_medium=email&utm_source=footer>.


--
Jörg Steffens joerg.s...@bareos.com
Bareos GmbH & Co. KG Phone: +49 221 630693-91
https://www.bareos.com

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz