You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I TLS-connect a source client (libshout 2.4.3) to an Icecast 2.4.4 server, the connection works as expected and I'm able to upload an audio stream. However, when I close that connection (shout_close) and kill the client, the newly-created Icecast mount point persists on the Icecast status page, even after the client has been killed. I have to use Icecast's admin interface to manually remove that mount point. This is not the case for non-TLS connections; the mount point goes away when the client does.
I'm not sure if the problem is with libshout or with icecast. With a TLS client, is there more that needs to be done to fully close a TLS connection, other than call shout_close? Thanks for your time.
The text was updated successfully, but these errors were encountered:
When I TLS-connect a source client (libshout 2.4.3) to an Icecast 2.4.4 server, the connection works as expected and I'm able to upload an audio stream. However, when I close that connection (shout_close) and kill the client, the newly-created Icecast mount point persists on the Icecast status page, even after the client has been killed. I have to use Icecast's admin interface to manually remove that mount point. This is not the case for non-TLS connections; the mount point goes away when the client does.
I'm not sure if the problem is with libshout or with icecast. With a TLS client, is there more that needs to be done to fully close a TLS connection, other than call shout_close? Thanks for your time.
The text was updated successfully, but these errors were encountered: