Wowza Community

Error message in log: Http2Connection GO_AWAY Frame received


I recently played around with LL-HLS, which also meant that I added the <AllowHttp2> tag to the VHost.xml:


Since then, I sometimes get the following warning messages in the logs during regular HLS livestreamings:

Http2Connection[Socket:/X.X.X.X:54171]: GO_AWAY Frame received. Error code: 1:PROTOCOL_ERROR, DebugInfo: Failed ping.]. Time: 1614859996044
Http2Connection[Socket:/X.X.X.X:54173]: GO_AWAY Frame received. Error code: 1:PROTOCOL_ERROR, DebugInfo: Failed ping.]. Time: 1614860016282
Http2Connection[Socket:/X.X.X.X:54174]: GO_AWAY Frame received. Error code: 1:PROTOCOL_ERROR, DebugInfo: Failed ping.]. Time: 1614860036521

X.X.X.X is the viewer’s ip. The stream seems to work fine (it’s regular HLS, not LL-HLS), but apparently a couple of users could be having problems? Or is this message something that’s not worth worrying about? What does it mean?

Thanks in advance.

Hmmm…the only time I’ve seen that @Bernhard_Schmidt is when the device or player being used was not compatible with LL-HLS. When that error appears, we typically share the following information since the protocol and the support for it is out of our control. Have you tested it on the following?

**You can test LL-HLS streams by entering the playback URL in the Safari browser on iOS 14, other native apps on devices running iOS 14, or any player that supports LL-HLS. If a player supports HLS but not LL-HLS, it will default to playing LL-HLS streams as standard HLS. **

Currently, only iOS 14+ Safari and THEOPlayer support LL-HLS.

Well, I’m not using LL-HLS in this application, it’s just a regular live application. The only thing that changed, is the AllowHttp2 in the VHost.xml. Could this be a problem? I wouldn’t think it’d interfere.
If it causes problems, I can take this setting out, but I’d like to keep it for future testings with LL-HLS.

The player btw is the JWPlayer 8.19.0, which should support LL-HLS in their latest release…but it doesn’t matter, as it was just a regular HLS stream, the application was neither configured nor intended for LL-HLS.

Nevermind, I disabled AllowHttp2, which also made the error messages go away. :wink:
I’ll have to run more tests on LL-HLS anyway, before it could be used in production…we’re still having problems with Safari and ABR, but that’s a different topic.

Ok sorry, thanks for telling me it was just regular HLS. So the Go-AWAY error is related to HTTP2 and can happen when there is a redirect attempt where HTTP2 is not supported or in a load balancer.

Here is some info on that error for you:

The GOAWAY frame (type=0x7) is used to initiate shutdown of a
connection or to signal serious error conditions. GOAWAY allows an
endpoint to gracefully stop accepting new streams while still
finishing processing of previously established streams.

If you’d like us to troubleshoot and see exactly where your clients may be running into an issue with it, feel free to submit a support ticket and we’ll try to replicate the error in some tests.