I have a running discourse installation (two actually, one in stage another in production, different vms and all). I’m testing on the staging environment. Installation via the official guide . Currently there is a Grafana/Prometheus/Node Exporter stack deployed via docker compose on the same VM wher…

Good find but if I try to target that specific port I get a “connection refused” message. Get "http://discourse_app:9405/metrics": dial tcp 172.20.0.2:9405: connect: connection refused Tested with a wget from inside the prometheus container as well just to be sure. /prometheus # ping discourse_ap…

Just to further poke into it I tried generating an API key from Discourse and reach it using the internal hostname and the response is not a 301, which is right because every request is supposed to be redirected to https. [image] The problem, I think, is that requests coming in, even if from an i…

You so have the prometheus plugin installed and enabled? It should allow requests from private addresses, but your could try setting the environment variable to allow access from the ip you’re pulling from.

Yep, Prometheus is on the same VM and deployed as a docker container. Everything works (I’ve other exporters deployed as well) but for some reason the Discourse Prometheus plugin, even if being clearly up and running, is not accepting requests. When you say the ENV variable you are talking about th…

[imagen] Crius: A ./launcher restart app should suffice for the envs to be picked up right? I would think so, but I’m not entirely sure. You can test from inside the container and see if you can curl it from there.

Running a wget from the prometheus container return: /prometheus # wget http://vmi1229594-app:80/metrics Connecting to vmi1229594-app:80 (172.20.0.2:80) Connecting to [public URL] (172.67.69.84:443) wget: note: TLS certificate validation not implemented wget: server returned error: HTTP/1.1 404 Not…

[imagen] Crius: guessing here that it’s the automatic redirect from the Discourse nginx container? Sounds right. You need to access it using the host name, not the container name.

I’m using the hostname, I wrote a lot and late, might have been confusing but definitely using the internal network hostname.

This is not my area of expertise, but I’ve had a rummage in the posts that the topic timer ate to see if any could be relevant, and possibly found these? (My apologies if I’m way off :slight_smile: :pray: ) Getting Discourse to see the Prometheus server IP - #5 by ishan Using Prometheous with Clou…

Thanks @JammyDodger but unfortunately those resources didn’t help. They have similar issue but slightly different to the point that they don’t apply in this case. Just to be sure, I tried what one of those topics suggested (as well as @pfaffman ) and played around with the DISCOURSE_PROMETHEUS_TRUS…

[imagen] Jay Pfaffman: You need to access it using the host name, not the container name. What Jay meant here is that you need to use the configured hostname (DISCOURSE_HOSTNAME in your container .yml definition) as opposed to any hostname that happens to resolve to the correct IP. This is d…

El trabajo de scrapeo de Prometheus no puede alcanzar las métricas

Soporte Instalación

pfaffman (Jay Pfaffman) 15 Mayo, 2023 00:40 7

Suena bien. Necesitas acceder a él usando el nombre de host, no el nombre del contenedor.

Tema		Respuestas	Vistas
Getting Discourse to see the Prometheus server IP Self-hosting prometheus	6	815	28 Junio 2020
Discourse Prometheus Plugin official , prometheus	5	20012	22 Octubre 2025
How to configure monitoring of discourse-prometheus on prometheus Extras	1	1249	17 Marzo 2022
Prometheus pluging Cross-Origin Request Support unsupported-install	1	970	21 Mayo 2020
Discourse Prometheus 404 metrics for Grafana Support prometheus	2	87	29 Octubre 2025

El trabajo de scrapeo de Prometheus no puede alcanzar las métricas

Temas relacionados