TLS handshake error

[Mark Dayton]

Hi Alan, thanks for the email. Radiusd -x isn't working on this version of
Alpine Linux so all I have is the tail log.

Below is what it reports when a connection attempt is made.

In the meantime I will read through the help info.

ERROR: (45) eap_tls: ERROR: (TLS) Alert write:fatal:handshake failure
ERROR: (45) eap_tls: ERROR: (TLS) Server : Error in error

On Wed, 19 Jun 2024, 8:54 pm Alan DeKok, <aland at deployingradius.com> wrote:

> On Jun 19, 2024, at 3:45 PM, Mark Dayton <m4rk.dayton at gmail.com> wrote:
> >
> > Hi, yes I've had that before and Microsoft have had to allow udp for the
> > tenant. I'm not sure if this is related though as it's not behind a load
> > balancer? I'm targeting the public IP of the container instance.
> >
> > The tail logs don't give a lot of information to be honest, is there any
> > other way of getting better logs?
> >
> > Would you suggest switching to radsec?
>
>   Switching to RadSec won't help with EAP-TLS errors.
>
>   What will help is reading the documentation and doing what it says:
> http://wiki.freeradius.org/list-help
>
>  What definitely does *not* help is saying "I couldn't see anything in the
> debug output, so I'm not going to post it".
>
>  The documentation says to post it.  So you should do that.  At least in
> part because the people here *understand* the debug output, and perhaps can
> see something that you missed.
>
>   So... follow the documentation and get help, or avoid the documentation
> and fail to make progress.  It's up to you.
>
>   Alan DeKok.
>
>
> -
> List info/subscribe/unsubscribe? See
> http://www.freeradius.org/list/users.html
>