Googling for that error: https://stackoverflow.com/questions/57420833/tls-no-renegotiation-error-on-http-request
However, as far as I can see, Prometheus doesn't have this option: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#tls_config You could try playing with min_version/max_version (see if you can tell which TLS version was used by curl) On Friday, 22 September 2023 at 11:59:24 UTC+1 Pragya Singh wrote: > I got a new error when I added enable_http2: false > local error : tls: no renegotiation > On Thursday, 14 September 2023 at 20:29:58 UTC+5:30 Brian Candler wrote: > >> Try this: >> >> enable_http2: false >> On Thursday, 14 September 2023 at 14:22:18 UTC+1 Pragya Singh wrote: >> >>> We are getting this error in prometheus while connecting to an endpoint >>> Get "https://10.14.0.42:443/health <https://10.14.0.42/health>": stream >>> error: stream ID 7; HTTP_1_1_REQUIRED; received from peer >>> >>> When checked manually: curl https://10.14.0.42:443/health >>> <https://10.14.0.42/health> -k -v --http1.1 >>> This works fine and provides list of metrics >>> >>> I added scheme: http but that didn't work and I am getting the same >>> error. Something like this >>> scrape_configs: >>> - job_name: 'example' >>> scheme: http >>> >>> Any recommendations on what else I can try here? >>> >>> >>> Regards, >>> Pragya >>> >> -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/d6d397b8-6a36-43cc-9f69-046564aa9bb0n%40googlegroups.com.
