This is a new error that just started cropping up. I suspect it's related to recent SSH changes. This might help a little with context, when it happens again.