Error stream error in the http 2 framing layer

Hi guys,

I have installed latest OMS agent on Debian 10.
When I have tried to configure custom log collection — configuration has been completed successfully, however data collection is failing.

As I can see — there is a connectivity error:

root@mrvserversmall:/opt/microsoft/omsconfig/Scripts# runuser -l omsagent -c /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py
Opened the dsc host lock file at the path ‘/opt/dsc/dsc_host_lock’
Error occured during operation PerformRequiredConfigurationChecks. r = 1
{
«ErrorType»: null,
«OtherErrorType»: null,
«OwningEntity»: «OMI:CIMOM»,
«MessageID»: «OMI:MI_Result:1»,
«Message»: «cURL failed to perform on this base url: we-agentservice-prod-1.azure-automation.net with this error message: Stream error in the HTTP/2 framing layer. Make sure cURL and SSL libraries are up to date.»,
«MessageArguments»: [],
«PerceivedSeverity»: 7,
«ProbableCause»: 0,
«ProbableCauseDescription»: «Unknown»,
«RecommendedActions»: null,
«ErrorSource»: null,
«ErrorSourceFormat»: null,
«OtherErrorSourceFormat»: null,
«CIMStatusCode»: 1,
«CIMStatusCodeDescription»: null,
«OMI_Code»: 1,
«OMI_Category»: 0,
«OMI_Type»: «MI»,
«OMI_ErrorMessage»: «A general error occurred, not covered by a more specific error code.»
}
Operation failed.

Error occured during operation PerformRequiredConfigurationChecks. r = 1
{
«ErrorType»: null,
«OtherErrorType»: null,
«OwningEntity»: «OMI:CIMOM»,
«MessageID»: «OMI:MI_Result:1»,
«Message»: «cURL failed to perform on this base url: we-agentservice-prod-1.azure-automation.net with this error message: Stream error in the HTTP/2 framing layer. Make sure cURL and SSL libraries are up to date.»,
«MessageArguments»: [],
«PerceivedSeverity»: 7,
«ProbableCause»: 0,
«ProbableCauseDescription»: «Unknown»,
«RecommendedActions»: null,
«ErrorSource»: null,
«ErrorSourceFormat»: null,
«OtherErrorSourceFormat»: null,
«CIMStatusCode»: 1,
«CIMStatusCodeDescription»: null,
«OMI_Code»: 1,
«OMI_Category»: 0,
«OMI_Type»: «MI»,
«OMI_ErrorMessage»: «A general error occurred, not covered by a more specific error code.»
}
Operation failed.

I have checked CURL:
libcurl3-gnutls is already the newest version (7.64.0-4).
libcurl4 is already the newest version (7.64.0-4).

also:
l:~# ls -la /opt/omi/lib/libcurl.so*
lrwxrwxrwx 1 root root 34 Oct 13 21:37 /opt/omi/lib/libcurl.so.3 -> /lib/x86_64-linux-gnu/libcurl.so.4
lrwxrwxrwx 1 root root 34 Oct 13 21:37 /opt/omi/lib/libcurl.so.4 -> /lib/x86_64-linux-gnu/libcurl.so.4

Can anyone help me how to solve this?

Regards,
Lewis

1. Home

2. php — Error: Stream error in the HTTP/2 framing layer

985 votes

1 answers

Get the solution ↓↓↓

I am working on my Graduation Project. We make our database using Laravel And MYSQL, then we made The API for the mobile app and uploaded it on 000webhost to use it online.

Before uploaded, we tried every single method on INSOMNIA locally and works fine,
but when we try it online only GET and POST methods work and when we try to use DELETE method we get this errorError: Stream error in the HTTP/2 framing layer.

Can you help us please.

2021-11-13

Write your answer

---

265

votes

Answer

Solution:

000webhost does not allow any other HTTP method except GET, POST, and HEAD.

So, Instead of a FREE plan, you will have to choose a PAID plan for use all HTTP methods.

---

Share solution ↓

Additional Information:

Date the issue was resolved:

2021-11-13

Link To Source

Link To Answer
People are also looking for solutions of the problem: composer detected issues in your platform: your composer dependencies require a php version «>= 7.3.0».

Didn’t find the answer?

Our community is visited by hundreds of web development professionals every day. Ask your question and get a quick answer for free.

---

Similar questions

Find the answer in similar questions on our website.

Write quick answer

Do you know the answer to this question? Write a quick response to it. With your help, we will make our community stronger.

About the technologies asked in this question

PHP

PHP (from the English Hypertext Preprocessor — hypertext preprocessor) is a scripting programming language for developing web applications. Supported by most hosting providers, it is one of the most popular tools for creating dynamic websites.
The PHP scripting language has gained wide popularity due to its processing speed, simplicity, cross-platform, functionality and distribution of source codes under its own license.
https://www.php.net/

Laravel

Laravel is a free open source PHP framework that came out in 2011. Since then, it has been able to become the framework of choice for web developers. One of the main reasons for this is that Laravel makes it easier, faster, and safer to develop complex web applications than any other framework.
https://laravel.com/

MySQL

DBMS is a database management system. It is designed to change, search, add and delete information in the database. There are many DBMSs designed for similar purposes with different features. One of the most popular is MySQL.
It is a software tool designed to work with relational SQL databases. It is easy to learn even for site owners who are not professional programmers or administrators. MySQL DBMS also allows you to export and import data, which is convenient when moving large amounts of information.
https://www.mysql.com/

Stream error in the HTTP/2 framing layer. Make sure cURL and SSL libraries are up to date. #1056

Comments

mrvladis commented Oct 14, 2019

I have installed latest OMS agent on Debian 10.
When I have tried to configure custom log collection — configuration has been completed successfully, however data collection is failing.

As I can see — there is a connectivity error:

root@mrvserversmall:/opt/microsoft/omsconfig/Scripts# runuser -l omsagent -c /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py
Opened the dsc host lock file at the path ‘/opt/dsc/dsc_host_lock’
Error occured during operation PerformRequiredConfigurationChecks. r = 1
<
«ErrorType»: null,
«OtherErrorType»: null,
«OwningEntity»: «OMI:CIMOM»,
«MessageID»: «OMI:MI_Result:1»,
«Message»: «cURL failed to perform on this base url: we-agentservice-prod-1.azure-automation.net with this error message: Stream error in the HTTP/2 framing layer. Make sure cURL and SSL libraries are up to date.»,
«MessageArguments»: [],
«PerceivedSeverity»: 7,
«ProbableCause»: 0,
«ProbableCauseDescription»: «Unknown»,
«RecommendedActions»: null,
«ErrorSource»: null,
«ErrorSourceFormat»: null,
«OtherErrorSourceFormat»: null,
«CIMStatusCode»: 1,
«CIMStatusCodeDescription»: null,
«OMI_Code»: 1,
«OMI_Category»: 0,
«OMI_Type»: «MI»,
«OMI_ErrorMessage»: «A general error occurred, not covered by a more specific error code.»
>
Operation failed.

Error occured during operation PerformRequiredConfigurationChecks. r = 1
<
«ErrorType»: null,
«OtherErrorType»: null,
«OwningEntity»: «OMI:CIMOM»,
«MessageID»: «OMI:MI_Result:1»,
«Message»: «cURL failed to perform on this base url: we-agentservice-prod-1.azure-automation.net with this error message: Stream error in the HTTP/2 framing layer. Make sure cURL and SSL libraries are up to date.»,
«MessageArguments»: [],
«PerceivedSeverity»: 7,
«ProbableCause»: 0,
«ProbableCauseDescription»: «Unknown»,
«RecommendedActions»: null,
«ErrorSource»: null,
«ErrorSourceFormat»: null,
«OtherErrorSourceFormat»: null,
«CIMStatusCode»: 1,
«CIMStatusCodeDescription»: null,
«OMI_Code»: 1,
«OMI_Category»: 0,
«OMI_Type»: «MI»,
«OMI_ErrorMessage»: «A general error occurred, not covered by a more specific error code.»
>
Operation failed.

I have checked CURL:
libcurl3-gnutls is already the newest version (7.64.0-4).
libcurl4 is already the newest version (7.64.0-4).

# ls -la /opt/omi/lib/libcurl.so*
lrwxrwxrwx 1 root root 34 Oct 13 21:37 /opt/omi/lib/libcurl.so.3 -> /lib/x86_64-linux-gnu/libcurl.so.4
lrwxrwxrwx 1 root root 34 Oct 13 21:37 /opt/omi/lib/libcurl.so.4 -> /lib/x86_64-linux-gnu/libcurl.so.4

The text was updated successfully, but these errors were encountered:

Источник

Stream error in the HTTP/2 framing layer #1537

Comments

rafonsecad commented Aug 18, 2020

Subject of the issue

As soon as I try to scan a wordpress site which has HTTP/2, I get the following error
Scan Aborted: The url supplied xxx seems to be down (Stream error in the HTTP/2 framing layer)

Your environment

• Version of WPScan: 3.8.6
• Version of Ruby: 2.7.1
• Operating System (OS): Docker version

Steps to reproduce

Simply scan any HTTP/2 wordpress website on WPScan docker.

Expected behavior

WPScan should start normally.

Actual behavior

As stated earlier, the following error messages appears
Scan Aborted: The url supplied xxx seems to be down (Stream error in the HTTP/2 framing layer)

What have you already tried

I guess this is an issue related to curl or libcurl. I followed this ticket and this one, In both cases the libcurl version is 7.64.x and it seems those were fixed in later versions.
Nevertheless WPScan in docker has the libcurl version 7.69.x so this issue should not happen anymore. Even in my machine, I’ve got curl version 7.68.0 and works without any problems against HTTP/2 webs.
I changed the origin base image to force a change in libcurl version in the Dockerfile, I set the base image on ruby:2.71-alpine so the libcurl version changed to 7.67, but the problem still persists.

Things you have tried (where relevant):

• Update WPScan to the latest version [ Yes]
• Update Ruby to the latest version [ Yes]
• Ensure you can reach the target site using cURL [ Yes]
• Ensure you are using a supported Operating System (Linux and macOS) [ Yes]

The text was updated successfully, but these errors were encountered:

Источник

«Error in the HTTP2 framing layer» after 1000 requests #3750

Comments

TvdW commented Apr 8, 2019 •

I did this

This started out as doing several thousand requests to some company’s API, and getting occasional errors stating «Error in the HTTP2 framing layer». It was found out that this always happened with stream id 7d1 (2001), also known as request 1001. This lead me to http2_max_requests in nginx. A few hours of minimizing the test case later, I’ve found two ways to reproduce this bug, generating different errors for the same task, when they should both just work fine.

Method one

The sleep server from my previous bug report returns 🙂 nginx is running on the server with http2_max_requests set to 10, for easier debugging. The sleep server just sleeps the given amount of milliseconds, and the issue seems to become reproducible around 5ms, but consistently so around 100ms.

Running the command above will execute 11 requests (one more than the limit). The last request times out, but there’s no reason for it to.

Method two

This uses the multi socket api, and produces the «Error in the HTTP2 framing layer» error message: https://gist.github.com/TvdW/a8bf6eabc99bf812d2fd0be1d32f9313

It’s a crude eventloop implementation doing the bare minimum for making the multi socket API work. This is the last version of my code before I managed to reproduce the bug using the curl command line utility. What’s notable about it is that it reproduces the issue, but with a different error message.

curl/libcurl version

operating system

thoughts

Some things stand out:

• this is only reproducible for requests with bodies, and only if they are not zero-length
• timing seems to matter. setting the ‘time’ component of the sleep server to 0ms makes the final request succeed quite often (maybe half the time), but when set to 100ms it seems to fail in 95% of cases or more
• the two methods produce very different error messages

The text was updated successfully, but these errors were encountered:

bagder commented Apr 8, 2019

Tricky. I tried both of your versions and I’ve not made any of them error for me, in spite of me having run both versions tens of times. I’ve tried both my 7.65.0-DEV version and my 7.64.0 system install!

kdudka commented Apr 8, 2019

We had a similar bug report in Fedora: https://bugzilla.redhat.com/1690971 . but it was resolved (or worked around) server-side.

TvdW commented Apr 8, 2019 •

I realized I forgot to add to the report that this is happening behind a HTTP proxy 😞 . It didn’t seem too relevant at the time of writing, but I’m now increasingly convinced that the proxy is changing some behavior on the TCP level, making the issue much more likely to occur. Yay for automatic configuration from environment variables 😄

The last two requests look like this:

Those are streams 0x13 (19) and 0x15 (21). The second one is supposed to fail (or not happen at all), because http2_max_requests is 10.

What stands out most are these:

• TLSv1.2 (IN), TLS alert, close notify (256):
• Connection #0 to host proxy left intact

In cases where it works properly, I see these:

• Closing connection 0
• TLSv1.2 (OUT), TLS alert, close notify (256):

I suspect there’s an issue here around how the tls alerts are handled. But, it sounds like that may be really hard to reproduce.

[edit] I’m able to reproduce this on the latest ‘alpine’ docker image, by running ‘apk add curl’ (adds 7.64.0), and then running the relevant command. Only when setting the https_proxy environment variable, though. So there’s definitely some proxy magic going on on the TCP level.

Источник

Getting «Stream error in the HTTP/2 framing layer» when uploading symbols #615

Comments

phillipCouto commented Oct 31, 2019

Here is the snippet from the console when running the sentry-symbols.js file from the sentry-wizard utility.

This is a on-premise installation running version 9.1.2. Let me know what other information I can provide to help resolve this issue.

The text was updated successfully, but these errors were encountered:

nbolender commented Nov 9, 2019

@phillipCouto Any luck with this?

sertony commented Nov 18, 2019

It’s rather connected to macOS Catalina, since we don’t have this issue on Mojave.
What OS do you use?

phillipCouto commented Nov 18, 2019

I am on macOS Catalina, 10.15.1 (19B88) to be exact.

I was going to try running the source code directly on my machine and debug it from that. Just haven’t had a chance yet as I moved off to other tasks.

nbolender commented Nov 18, 2019

@sertony I’m suspecting as much as well, since it occurred after upgrading to Catalina (10.15.1). The system curl version is curl 7.64.1 (x86_64-apple-darwin19.0) libcurl/7.64.1 (SecureTransport) LibreSSL/2.8.3 zlib/1.2.11 nghttp2/1.39.2 .

I am not sure how to upgrade curl and get sentry-cli to use it without replacing the system version. Any thoughts?

For now, I have disabled http2 on my sentry server.

phillipCouto commented Nov 18, 2019 •

@nbolender I was trying to do the same but since Sentry is behind a reverse proxy I was having a hard time disabling HTTP2 only for sentry.

I have more evidence that it is a macOS issue. I have a CI job that runs in a docker container and it is uploading fine. Just curious couldn’t a rust HTTP client that supports http2 be used instead of linking to curl?

sertony commented Nov 18, 2019

@nbolender curl update didn’t work for me either (did it via homebrew), and I haven’t tried downgrading. We have just disabled HTTP2 on our server too for now. No other thoughts.

nbolender commented Nov 18, 2019

@sertony Homebrew specifically does not replace the system version at /usr/bin/curl since many things may rely on it, so I’m not sure that sentry-cli will use the homebrew version.

sertony commented Nov 19, 2019

@nbolender yep, you are right. That’s why I added export PATH=»/usr/local/opt/curl/bin:$PATH» to my bash_profile, but apparently it didn’t help.

phillipCouto commented Nov 19, 2019

@sertony you need to recompile the cli to link to your custom location for the curl library not the executable.

cbounta commented Dec 3, 2019

I also met this issue, while using the latest gradle sentry android plugin(io.sentry.android.gradle 1.7.28). Any workarounds for this?

jan-auer commented Mar 3, 2020

Could you try again with sentry-cli v 1.51.1 ? We started to link libcurl statically.
cc @kamilogorek

kamilogorek commented Mar 6, 2020

Closing the issue as a part of large repository cleanup, due to it being inactive and/or outdated.
Please do not hesitate to ping me if it is still relevant, and I will happily reopen and work on it.
Cheers!

notjosh commented Apr 6, 2020

fwiw, for anyone stumbling on this later, updating (from 1.49.0 to 1.52.1 in my case) fixed the issue on Catalina

spidey commented Feb 15, 2021

I’m not using the sentry-cli but rather sending requests directly through curl on Mac, and also getting a similar error: curl: (92) HTTP/2 stream 1 was not closed cleanly: PROTOCOL_ERROR (err 1) .

Workaround was to force HTTP/1.1 on curl with option —http1.1 . Not an option on sentry-cli I imagine.

Источник

» Stream error in the HTTP/2 framing layer» #32

Comments

mdsumner commented Oct 5, 2016 •

I don’t have anything to offer here, just listing this in case it’s helpful.

I submitted check runs today from a different machine (Windows), same email, by first using validate_email().

On second machine (also Windows) I can’t get it to work.

Try with token from earlier today.

I tried again moving across to Debian, installing from github then validate_email — I got the new token and proceeded ok.

The text was updated successfully, but these errors were encountered:

jeroen commented Oct 5, 2016

@gaborcsardi does this still happen after you disabled HTTP2 on the server??

gaborcsardi commented Oct 5, 2016

I disabled it about an hour ago (again, it crept back, nginx config is autogenerated), I hope these happened before that.

@mdsumner can you please try it now?

jeroen commented Oct 5, 2016

jeroen commented Oct 5, 2016

Your server is still advertising HTTP/2 support.

gaborcsardi commented Oct 5, 2016

OK, should be off now.

I had to turn it off for all dokku web apps.

mdsumner commented Oct 5, 2016

«Build started . » — working now, thanks!

gaborcsardi commented Oct 5, 2016

OK, I fixed this in my own dokku installation, so it should not come up again. To be extra sure, I’ll also disable http2 in the R package: #29

jeroen commented Oct 5, 2016

I would recommend against disabling HTTP/2 on the client, so that you will catch server problems if they (re)appear. Other http/rhub clients might also default to HTTP/2 if the server has it enabled.

gaborcsardi commented Oct 5, 2016

That is true in general, I agree.

But I also do not anticipate other clients (just yet), and hopefully the dokku/nginx problems are temporary, so I can enable http2 again soon.

My problem is that I don’t use Windows/Linux daily, so I don’t notice the problems if they reappear, and there is also nothing in the nginx logs about them.

Anyway, you have a good point, so I’ll think about this before disabling it. Maybe I should just set up some daily test builds, submitted from various OSes. Should be pretty easy to do this on the other Jenkins instance that I already have for management.

Источник