Brian Ehlert comments

Results 156 comments of


                                            Brian Ehlert

hello i'm using prometheus to monitor nginx i got this error ""2022/05/09 14:31:49 Starting NGINX Prometheus Exporter Version=0.4.2 GitCommit=f017367 2022/05/09 14:31:49 Could not create Nginx Client: failed to get http://172.17.0.1:9113/stub_status: Get http://172.17.0.1:9113/stub_status: read tcp 192.168.96.3:40334->172.17.0.1:9113: read: connection reset by peer""

Did you: `For NGINX, expose the [stub_status page](https://nginx.org/en/docs/http/ngx_http_stub_status_module.html#stub_status) at /stub_status on port 8080.` As mentioned in the readme?

createClientWithRetries should be revised

If you are willing to create the PR, please do so.

Add metrics form NGINX Plus API version 7

Comment added by Brian Ehlert in Aha! - [View](https://nginx.aha.io/comments/7076580326181839157) I was reading through the Prometheus exporter and I think this might already be supported. Someone would need to verify. Please.

Enabling IPv6 causes Client.Timeout exceeded while awaiting headers since 0.9.0

I have a feeling this is related to IPv6 We have a future plan to properly support IPv6

Enabling IPv6 causes Client.Timeout exceeded while awaiting headers since 0.9.0

Are you IPv6 alone? or dual stack? And if dual stack is the IPv4 address being used.

Fix for CVE-2022-21698

We generally follow a quarterly release cycle for this and the related projects. The current target for that is the start of October. Is there a belief that through how...

NGINX Kubernetes POD goes into a crashloopback.

The solution can still apply. The only difference is nginx vs nginx plus - the rest of the code is the same.

help , my kubernetes version is 1.18.0, I update my nginx-ingress1.7.2 to 1.11.0, tip error.

It looks as if your RBAC settings need to be updated. However, I believe you are asking about a problem with the NGINX Ingress Controller maintained by the community, which...

proxy_next_upstream doesn't work for nginx/nginx-ingress:2.2.2

The Ingress resource and the CRDs TransportServer and VirtualServer resources can co-exist. The catch is that any single hostname can only be defined using one or the other. And that...

proxy_next_upstream doesn't work for nginx/nginx-ingress:2.2.2

Hey @AndriiPasternak1989 Since you raised this issue we have been having a bit of an internal debate about your full use case (not just this single setting). I am guessing...