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
I've upgraded my old status bot node to the newest node version. Previous version was v0.8.7 now we run v0.10.5.
Since I upgraded, the status bot doesn't connect properly anymore. We run OpenSSH_5.3p1 and the secure log states the following;
May 5 14:04:01 sshd[7780]: Bad packet length 1469807856.
May 5 14:04:21 sshd[7811]: Bad packet length 3010211349.
May 5 14:04:41 sshd[7821]: Bad packet length 2215667743.
May 5 14:05:01 sshd[7832]: Bad packet length 2092073108.
May 5 14:05:21 sshd[7846]: Bad packet length 2416978723.
May 5 14:05:41 sshd[7861]: Bad packet length 3922530746.
May 5 14:06:01 sshd[7872]: Bad packet length 3756914114.
May 5 14:06:21 sshd[7879]: Bad packet length 1458609236.
May 5 14:06:41 sshd[7886]: Bad packet length 2811535146.
May 5 14:07:01 sshd[7895]: Bad packet length 1332097811.
(on each connection attempt).
I tried:
Basic AUTH
Key AUTH
I tried versions:
v0.10.5 (not working auth)
v0.10.4 (not working auth)
v0.10.2 (not working auth)
v0.9.12 (not working auth)
v0.9.4 (not working auth)
v0.8.23 (works)
It seems that the node upgrade does have impact on this combination. I will try to debug it more and hopefully even fix it. But in the hope there already is a fix; this issue.
The text was updated successfully, but these errors were encountered:
Oh my facepalmness, works. Thank you for waking me up :) haha, I've = in my package.json instead of >= (I use your module happily for a while already).
I've upgraded my old status bot node to the newest node version. Previous version was v0.8.7 now we run v0.10.5.
Since I upgraded, the status bot doesn't connect properly anymore. We run
OpenSSH_5.3p1
and the secure log states the following;(on each connection attempt).
I tried:
I tried versions:
It seems that the node upgrade does have impact on this combination. I will try to debug it more and hopefully even fix it. But in the hope there already is a fix; this issue.
The text was updated successfully, but these errors were encountered: