-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
[Bug]: grpc server address does not follow app.toml #18172
Comments
So what's the exact problem? |
We are running multiple cosmos nodes on one machine. Without changing the port, we want to specify an internal IP and listen to 9090 grpc for each specific address. For example, There is an IP that grpc listens to in app.toml, but I am curious as to whether hard coding is used instead of using the value. |
dont see a reason to hardcode it, we can just default it 127.0.0.1 |
The current code does not use the default value. In the grpc address value of app.toml, the address is ignored and only the port is used. And it uses the hard coded address 127.0.0.1. |
Is there an existing issue for this?
What happened?
There is a config in
app.toml
that can set the address of the grpc server.In most cases, 127.0.0.1 will be used, but there are sometimes when internal IP or DNS must be used depending on internal policy.
cosmos-sdk/server/start.go
Line 501 in 03bca7b
At that point the problem occur. Is there any other reason to hard code it?
Cosmos SDK Version
0.46, 0.47 and main
How to reproduce?
No response
The text was updated successfully, but these errors were encountered: