Errors when proxy is defined

[abrrco]

What did you do?
Download and start Prometheus 2.0

What did you expect to see?
Prometheus running

What did you see instead? Under which circumstances?

If HTTP_PROXY and/or HTTPS_PROXY is set in environment, on
Ubuntu 16.04:
transport: http2Client.notifyError got notified that the client transport was broken unexpected EOF.
Ubuntu 14.04:
2017/11/27 13:18:51 grpc: addrConn.resetTransport failed to create client transport: connection error: desc = "transport: failed to do connect handshake, response: "HTTP/1.1 407 Proxy Authentication Required\r\nConnection: close\r\nContent-Length: 849\r\nCache-Control: no-cache\r\nContent-Type: text/html; charset=utf-8\r\nPragma: no-cache\r\nProxy-Authenticate: NTLM\r\nProxy-Authenticate: BASIC realm=\"IWA_Almbrand\"\r\nProxy-Connection: close\r\n\r\n\r\n<TITLE>Access Denied</TITLE>\r\n\r\n\r\n<FONT face=\"Helvetica\">\r\n
\r\n\r\n

\r\n<TABLE border=0 cellPadding=1 width=\"80%\">\r\n\r\n<FONT face=\"Helvetica\">\r\nAccess Denied (authentication_failed)\r\n
\r\n
\r\n\r\n\r\n\r\n<FONT face=\"Helvetica\">\r\nYour credentials could not be authenticated: \"Credentials are missing.\". You will not be permitted access until your credentials can be verified.\r\n\r\n\r\n\r\n<FONT face=\"Helvetica\">\r\nThis is typically caused by an incorrect username and/or password, but could also be caused by network problems.\r\n\r\n\r\n\r\n<FONT face=\"Helvetica\" SIZE=2>\r\n
\r\nFor assistance, contact your network support team.\r\n\r\n\r\n\r\n

\r\n\r\n\r\n""; Reconnecting to {[::]:9090 }

Keeps repeating in output

[abrrco]

uname -srm
Linux 4.4.0-97-generic x86_64 and
Linux 4.4.0-70-generic x86_64

prometheus, version 2.0.0 (branch: HEAD, revision: 0a74f98)
build user: root@615b82cb36b6
build date: 20171108-07:11:59
go version: go1.9.2

prometheus.yml is not changed.

proxy is defined as
HTTP_PROXY="http://user:password@server.domain.dk:8080"
I do not need the proxy for Prometheus, but this is a test server used for other purposes and I was wondering why Prometheus attempts to access the proxy.

Regards

Rene

[brian-brazil]

It makes more sense to ask questions like this on the prometheus-users mailing list rather than in a GitHub issue. On the mailing list, more people are available to potentially respond to your question, and the whole community can benefit from the answers provided.

[miso2018]

Setting NO_PROXY=...,0.0.0.0:9090,... resolves this. Prometheus is probably scraping your prometheus metrics endpoint and going through your proxy to do it.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.