"Reached end of stream but expected 4 more bytes."
jhertel opened this issue · 1 comments
I very often get the message "Reached end of stream but expected 4 more bytes." in red characters. When I get it, the function I want to call isn't executed.
I can find no pattern as to when I get it. If I give the command "expresso status" several times in a row, I sometimes get the wanted result:
VPN connected to 'Denmark' (78)
but other times:
Reached end of stream but expected 4 more bytes.
Here is an actual session in CMD; each command was executed within 1-2 seconds from the previous:
C:\ProgramsManual\Expresso>expresso status
Reached end of stream but expected 4 more bytes.C:\ProgramsManual\Expresso>expresso status
VPN connected to 'Denmark' (78)C:\ProgramsManual\Expresso>expresso status
Reached end of stream but expected 4 more bytes.C:\ProgramsManual\Expresso>expresso status
VPN connected to 'Denmark' (78)C:\ProgramsManual\Expresso>expresso status
Reached end of stream but expected 4 more bytes.C:\ProgramsManual\Expresso>expresso status
VPN connected to 'Denmark' (78)C:\ProgramsManual\Expresso>expresso status
VPN connected to 'Denmark' (78)C:\ProgramsManual\Expresso>expresso status
Reached end of stream but expected 4 more bytes.
I also get the "Reached end of stream but expected 4 more bytes." when issuing disconnect and connect commands, again unpredictably. Sometimes it works, other times it doesn't.
I even got this (!):
C:\ProgramsManual\Expresso>expresso.exe
Reached end of stream but expected 4 more bytes.
So executing expresso.exe with no arguments can even give "Reached end of stream but expected 4 more bytes." But not always. It will work again a few seconds later. And then after a few seconds again not.
This means that Expresso is unreliable as of now. It sometimes works, other times not.
And I really can't find any pattern to it. It's not like it always fails. It fails sometimes, but only sometimes. It's like tossing a coin.
The ExpressVPN GUI client works fine when I interact with it.
Versions:
ExpressVPN client: 10.17.0 (28)
Expresso: 1.3.0
OS: Windows 10 Home (10.0.19043)
I tried restarting the computer, but to no avail. Same problem.