[Icecast] Empty auth error message, URL auth problems on Windows Server

[Brad Isbell]

I'm having an issue with URL-based authentication on Windows Server that is
being aggravated by a separate logging issue.  In the server's error log:

[2020-03-13  16:59:46] DBUG connection/connection.c alias has made /player/
> into /player/index.html
> [2020-03-13  16:59:46] INFO auth/auth.c adding client for authentication
> [2020-03-13  16:59:46] DBUG auth/auth.c ...refcount on auth_t (default
> mount) is now 2
> [2020-03-13  16:59:46] INFO auth/auth.c auth on (default mount) has 1
> pending
> [2020-03-13  16:59:46] DBUG auth/auth.c 1 client(s) pending on (default
> mount)
> [2020-03-13  16:59:46] DBUG stats/stats.c update global clients (2)
> [2020-03-13  16:59:46] DBUG stats/stats.c update global connections (7)
> [2020-03-13  16:59:46] DBUG stats/stats.c update global client_connections
> (6)
>
> *[2020-03-13  16:59:46] WARN auth_url/auth_url.c auth to server
> https://auth.example.com/icecast/listenerAdd
> <https://auth.example.com/icecast/listenerAdd> failed with *[2020-03-13
>  16:59:46] DBUG auth/auth.c ...refcount on auth_t (default mount) is now 1
> [2020-03-13  16:59:46] DBUG fserve/fserve.c Adding client to file serving
> engine
> [2020-03-13  16:59:46] DBUG fserve/fserve.c fserve handler waking up
> [2020-03-13  16:59:46] DBUG fserve/fserve.c fserve handler exit
> [2020-03-13  16:59:46] DBUG stats/stats.c update global clients (1)


The key here is: *auth to server ... failed with [missing error message]*

It seems that at least in this particular case, the error message isn't
being logged.  Is this a bug with how Icecast is outputting the error
message, or an issue with libcurl?  I'm hoping if I can see the error
message, I can track down the main problem.

The main problem is that URL authentication with HTTPS doesn't seem to work
on Windows Server.  I can see that a TCP connection is being made to the
auth server, but the auth server says that the Icecast server resets the
connection before making a request.  I have not had this issue with Icecast
builds on Windows 10, nor Ubuntu.  I'm assuming there's some additional
security constraint preventing Icecast from using HTTPS for auth under
Windows Server.  The Windows Event Logs don't contain anything relevant.  I
have tested with proper public certificates from LetsEncrypt and DigiCert,
as well as self-signed certificates.

Any thoughts on either issue would be much appreciated.

Thanks,
*Brad Isbell // AudioPump, Inc.*
brad at audiopump.co
Skype: bradisbell
Phone: +1 312-488-4680
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20200313/a3f08e5e/attachment.htm>