The error "http2: unsupported scheme" might be affected by this setting:
# Whether to enable HTTP2. [ enable_http2: <boolean> <https://prometheus.io/docs/prometheus/latest/configuration/configuration/#boolean> | default: true ] Whether that will fix your problem I don't know. If you've deployed PushProx behind ALB, wouldn't it be accessed simply by connecting to its external URL which points to the outside of ALB? In that case you don't need "proxy_url" at all. That's for when you want the HTTP request to pass through an external proxy, like Squid. On Wednesday 20 March 2024 at 17:31:48 UTC Nikolay Buhryk wrote: > Hello > > I would like to use *proxy_url* for my job with hosts that not directly > accessible by Prometheus. > > PushProx proxy service > <https://github.com/prometheus-community/PushProx/tree/master> is > deployed behind AWS ALB with HTTPS, but for some reason, it doesn't work, > I'm always getting an error *context deadline exceeded* on the Prometheus > side. > > However proxy client on the host that I would like to scrape is able to > register itself via HTTPS > > When I tried to use it with HTTP, setting it in config as *proxy_url: > htttp://some_url *to have the possibility to redirect all calls to the > HTTPS by ALB it says *http2: unsupported scheme* > > Does the *proxy_url* parameter support HTTPS in the URL? > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/61e3ac04-551c-45c6-a075-58bb3bf0286an%40googlegroups.com.
