# NIOSSL: spurious uncleanShutdown error

**URL:** <https://forums.swift.org/t/niossl-spurious-uncleanshutdown-error/53031>\
**Category:** SwiftNIO\
**Created:** [October 24, 2021, 8:34pm UTC](https://forums.swift.org/t/niossl-spurious-uncleanshutdown-error/53031 "2021-10-24T20:34:07Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![taylorswift](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/taylorswift/32/43413_2.png) [@taylorswift](https://forums.swift.org/u/taylorswift)\
**Post date:** [October 25, 2021, 7:39pm UTC](https://forums.swift.org/t/niossl-spurious-uncleanshutdown-error/53031/3 "2021-10-25T19:39:07Z")

</div>

> [@lukasa](#):
>
> This is achieved by having the side that wants to initiate a close sending a `CLOSE_NOTIFY` alert on the TLS connection. The side that receives this alert should immediately send its own `CLOSE_NOTIFY` alert. Once that's done, it's safe to tear the TCP connection down.

i’m seeing this when i initiate the disconnect. does this mean i should be sending this alert from my end? if so, how do i do this?

---

_[View the full topic](https://forums.swift.org/t/niossl-spurious-uncleanshutdown-error/53031)._