Failed to start new stream error, MACOS 10.13 about greenlight

[placematts]

@ExcelsiorGamingYT, did you get prompted to update Greenlight to 2.0.0-beta15 and do so by clicking on the provided download button?

I think you may have run into the same issue that I did today, but I was able to overcome it by updating to the true latest release (2.3.1), which can be found here:
https://github.com/unknownskl/greenlight/releases

Here's my story:

I fired up Greenlight this afternoon for the first time in quite a while, so I wasn't surprised when I was prompted to update. I clicked on the provided download button and was taken to the following page for the 2.0.0-beta15 release:
https://github.com/unknownskl/greenlight/releases/tag/v2.0.0-beta15

Like a typical user, I didn't pay attention and thought I was getting the latest release. When I fired up 2.0.0-beta15 I was greeted by the same error as you:
Failed to start new stream. Error details {}

I did some basic troubleshooting and that's when I found your bug report. Shortly thereafter I made my way to .../greenlight/releases and found the current release is 2.3.1 and not the 2.0.0-beta15 that the Greenlight's built-in update mechanism pointed me to.

I have no idea what version of Greenlight I started with and from which I was prompted to update to 2.0.0-beta15, by the update mechanism.

For completeness:

Environment:

- OS: macOS Sonoma 14.4.1
- Device: Mac Stuidio M1 Max
- Greenlight version: Greenlight-2.0.0-beta15-universal and then Greenlight-2.3.1-universal

[falc410]

Ran into the same Problem and the solution from @placematts works perfectly. Issue can be solved I guess.

[ExcelsiorGamingYT]

Yes tried 2.3.1 but im unable to install it as im on high sierra and i get the circle with a line through it to say its incompatible

[placematts]

Yes tried 2.3.1 but im unable to install it as im on high sierra and i get the circle with a line through it to say its incompatible

I suggest trying some older releases (<2.3.1) and see if you can find one that is both compatible with High Sierra and free of the original issue you reported. But given how old macOS 10.13 is, you might be better off upgrading the OS, especially in the long run.