"Invalid session token" when connecting to Windows

[gaborcsardi]

Thank you for the great action!

For some reason I cannot connect to Windows any more. I get

...
debug1: Authentication succeeded (none).
Authenticated to nyc1.tmate.io ([134.209.128.51]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: Sending environment.
debug1: Sending env LANG = en_US.UTF-8
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Invalid session token
debug1: channel 0: free: client-session, nchannels 1
Connection to nyc1.tmate.io closed by remote host.
...

Happy to share more logs if that's helpful. Connecting to Linux still works, so maybe something has changed on the Windows runner? Anybody has ideas what this could be? Thanks!

EDIT: sometimes I get a slightly different error:

debug1: pledge: filesystem
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
Internal error
debug1: channel 0: free: client-session, nchannels 1
Connection to sfo2.tmate.io closed.

[3nids]

same here

[phanirithvij]

https://github.com/tmate-io/tmate/issues/322#issuecomment-3083622301

[Vampire]

Or to spell out the link content: It seems we need to search for a replacement. :-( tmate which this action is based on is dead, unless the author of this action (or anyone else) will effectively step-up and provide replacement servers. :-( https://github.com/tmate-io/tmate/issues/322#issuecomment-3083622301 For me not even SSH access works.

[phanirithvij]

There is upterm though I haven't tried it https://github.com/owenthereal/upterm

[Vampire]

Ignore what I said, SSH access works again for me, it probably just was a hiccup.

There is upterm though I haven't tried it

That's (for me) not a sufficient replacement currently.

• the original action repo is archived, but there is a new fork that is maintained now (just for those reading here)
• but the fork like the original does not support Windows which was the original reason I switched to this action

While I was hit by the SSH hiccup I also evaluated alternatives with the main requirement that they are working on all three major OS and are currently working. So just in case we finally do need to use an alternative, the best options I currently found were:

• indeed the action-upterm if Windows is not needed or maybe gets added
• debug-via-ssh but this has some restrictions, because you need an ngrok account for it and now they also require you to give a credit card to identify as non-abuser without it being charged, but some people might not have a credit card or don't want to provide it. And afair you are also restricted to one SSH session at a time in the free ngrok account which can also become cumbersome if you debug a matrix build, especially as there by default the session stays alive when you continue and there was no easy way to kill the ngrok session an on macOS could not even continue the job. There are alternatives using ngrok but this was the best I found from testing that also worked halfway.
• most probably the best replacement unless maybe action-upterm gets Windows support was actiondebugger-by-warpbuild, as warpbuild is a tmate fork iirc and their action is a fork of this action. Maybe it could even work to specify the warpbuild servers for this action if it stayed compatible, I did not try that.