Failed Attempt To Allocate Buffer Size about tabby-web

[Eugeny]

Could you please clarify?

[capriciousduck]

I SSHed to my VPS from Tabby Web. Then I run a command to unzip my Wordpress zip file. Then I got that error.

[Eugeny]

That isn't really a terminal issue.

[capriciousduck]

Sorry, I wasn't clear. A red popup appeared with the message: Bad Packet Length

…

On Mon, 7 Feb, 2022, 1:45 pm Eugeny, ***@***.***> wrote: Closed #47 <#47>. — Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI2VBQ3ZJRY3EGD3NCH4L2LUZ55TTANCNFSM5NWRRMWQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[bad1dea]

Having the same issue with this..

Getting random "bad packet length" and buffer allocate 0x7ffff size error when running random commands.

Even during random connections.. started happening after enabling vault to save ssh passwords

[milas]

I'm getting the same errors while self-hosting tabby-web and the gateway. They're both running behind nginx, and afaik I've got all the relevant websocket options on. In my testing, this is actually all on the same LAN (wired).

Usually, I can log in and run a few commands before I get the Error: Bad Packet Length error, but sometimes I get it before the connection even completes.

The other error, RangeError: Attempt to allocate Buffer larger than maximum size: 0x7fffffff bytes, appears less frequently, but when it does, it will initially appear alongside the bad packet length error, and will then appear every few seconds after that.

There's nothing of interest in the logs for either tabby-web or the gateway (or nginx for that matter).

[milas]

I realized this happens in Firefox but not Chrome.

I'm using Firefox 110.0 (64-bit) on AMD64 for reference. I'm happy to debug further if you have suggestions.