file attachments

comments

We updated our Chargify.net DLL to the latest version on Oct 15th which resolved all API issues.

Starting Oct 24th, and continuing through today, we have periods of a couple hours where we are receiving System.IO.IOException: Received an unexpected EOF or 0 bytes from the transport stream. This continues for a couple hours and then seemingly resolves itself.

The exceptions seem to show TLS being used to try and connect, the ServicePointManager default, then reverts to using SSL after a connection is unable to be made using TLS. We are still trying to determine if Chargify's API has changed or is changing, or if
something else is causing these temporary outages.