New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot derive external address port without listening on a secure port. #81870
Comments
You now have to put the IPv6 address in square brackets, then it works. I have no idea where the change comes from. Can't find anything in the release notes. |
Maybe now the listening is done by something like |
I think this is still a bug and the issue should be kept open. grafana/pkg/api/http_server.go Line 392 in 4b90936
This and the code in the following lines sound a lot like using IPv6 without brackets should be the default and also the used code referring to the http_addr value should use IPv6 without the brackets if I read the docs of the parseIP function right: https://pkg.go.dev/net#ParseIP The problem is that http_addr is parsed into HTTPAddr here grafana/pkg/setting/setting.go Line 1916 in eef491d
but I can't find any change of usage of that variable between v10.2.3 and v10.3.1 Maybe its a problem with a changed behavior of an upstream library. I would appreciate if you could reopen the issue and maybe change the title accordingly. |
Ok now after a little debugging I see the net.JoinHostPort function of Go returns a string like And go seems to expect a version with square brackets, see: "If the host is a literal IPv6 address it must be enclosed in square brackets, as in "[2001:db8::1]:80" or "[fe80::1%zone]:80"" https://pkg.go.dev/net#Dial So maybe some fallback code was removed in go. I would recommend trying to remove this line: https://github.com/grafana/grafana/blob/main/pkg/api/http_server.go#L393 |
Alright, I've reopened the issue. I'll try that fix soon |
In |
I had this issue as well, and the square brackets fixed it. However, I would also like to note that the error message in the title is an info-level message, and my config originally limited logging to 'warn', so it took a while to figure out what the real problem was (I kept thinking the errors about provisioning directories being missing (which I don't use) was the issue). |
Still seems to be a problem in 10.3.4...
|
@DmitriK It works for me, thx :) |
The reason is that the apiserver printed a fatal log and exited. i will fix it , hope next version this problem can be solved. |
finally, locate this line of code:https://github.com/grafana/grafana/blob/main/pkg/services/apiserver/config.go#L30 |
What happened?
What did you expect to happen?
For it to run normally, the config worked on an older version, my config is like so:
Did this work before?
Yes, 10.2.3
Is the bug inside a dashboard panel?
No response
Environment (with versions)?
Grafana: 10.3.1
OS: NixOS
Browser: -
Grafana platform?
A package manager (APT, YUM, BREW, etc.)
Datasource(s)?
The text was updated successfully, but these errors were encountered: