-
Notifications
You must be signed in to change notification settings - Fork 38
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
connection closed before server preface received #1351
Comments
cthulhu-rider
pushed a commit
to cthulhu-rider/neofs-node
that referenced
this issue
May 4, 2022
In previous implementation NeoFS CLI app used `network.Address.HostAddr` as a server URI, which caused scheme loss since host address doesn't container it. Add `internal.NetAddr` type with `DecodeString` method to be used by CLI app. Accept address of this type in `internal.GetSDKClient` function. Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
cthulhu-rider
pushed a commit
to cthulhu-rider/neofs-node
that referenced
this issue
May 4, 2022
In previous implementation NeoFS CLI app used `network.Address.HostAddr` as a server URI, which caused scheme loss since host address doesn't container it. Add `internal.NetAddr` type with `DecodeString` method to be used by CLI app. Accept address of this type in `internal.GetSDKClient` function. Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
@tasselsd thanks 4 ur report 😸 |
cthulhu-rider
pushed a commit
to cthulhu-rider/neofs-node
that referenced
this issue
May 4, 2022
In previous implementation NeoFS CLI app used `network.Address.HostAddr` as a server URI, which caused scheme loss since host address doesn't container it. Add `internal.NetAddr` type with `DecodeString` method to be used by CLI app. Accept address of this type in `internal.GetSDKClient` function. Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
cthulhu-rider
pushed a commit
to cthulhu-rider/neofs-node
that referenced
this issue
May 4, 2022
In previous implementation NeoFS CLI app used `network.Address.HostAddr` as a server URI, which caused scheme loss since host address doesn't contain it. Rename `HostAddr` to `URIAddr` and make it to return URI address with `grpcs` scheme if TLS is enabled. Make `TLSEnabled` unexported since it was used to provide default `tls.Config` only (it is used by default in SDK). Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
cthulhu-rider
pushed a commit
that referenced
this issue
May 5, 2022
In previous implementation NeoFS CLI app used `network.Address.HostAddr` as a server URI, which caused scheme loss since host address doesn't contain it. Rename `HostAddr` to `URIAddr` and make it to return URI address with `grpcs` scheme if TLS is enabled. Make `TLSEnabled` unexported since it was used to provide default `tls.Config` only (it is used by default in SDK). Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
aprasolova
pushed a commit
to aprasolova/neofs-node
that referenced
this issue
Oct 19, 2022
In previous implementation NeoFS CLI app used `network.Address.HostAddr` as a server URI, which caused scheme loss since host address doesn't contain it. Rename `HostAddr` to `URIAddr` and make it to return URI address with `grpcs` scheme if TLS is enabled. Make `TLSEnabled` unexported since it was used to provide default `tls.Config` only (it is used by default in SDK). Signed-off-by: Leonard Lyubich <leonard@nspcc.ru>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I got unexpected output when I use
neofs-cli
Expected Behavior
Can communicate correctly with storage node
Current Behavior
rpc error: write request: rpc error: code = Unavailable desc = connection closed before server preface received
Your Environment
The text was updated successfully, but these errors were encountered: