You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are scenarios where IPv6 is not working as expected, we should look into supporting it so the server doesn't generate errors or invalid configurations.
This investigation into IPv6 got triggered by: #4036
Some tested scenario's and their current results:
Single Node
Minimal secure configuration with any IP and:
Config:
IntIp: "::"
ExtIp: "::"
Curl:
curl -v --insecure --fail -X GET "https://admin:changeit@[::1]:2113/gossip"
[ 8332, 1,10:07:12.205,FTL] Host terminated unexpectedly.
System.Exception: Invalid format for gossip seed port: 4e34:7285:4620:ec38:485e:c3f8:cfc3]:2114
at EventStore.Core.ClusterVNodeOptions.ParseGossipEndPoint(String val) in D:\a\TrainStation\TrainStation\build\oss-eventstore\src\EventStore.Core\ClusterVNodeOptions.Framework.cs:line 70
[11640,22,11:09:56.920,INF] View Change Send Failed to "Unspecified/:::2114"
System.AggregateException: One or more errors occurred. (Status(StatusCode="Internal", Detail="Error starting gRPC call. HttpRequestException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName') ([::]:2114) ArgumentException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName')", DebugException="System.Net.Http.HttpRequestException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName') ([::]:2114)
---> System.ArgumentException: IPv4 address 0.0.0.0 and IPv6 address ::0 are unspecified addresses that cannot be used as a target address. (Parameter 'hostName')
...
at Grpc.Net.Client.Internal.GrpcCall2.RunCall(HttpRequestMessage request, Nullable1 timeout)")
at EventStore.Core.Cluster.EventStoreClusterClient.SendViewChangeAsync(Guid serverId, EndPoint serverHttpEndPoint, Int32 attemptedView, DateTime deadline) in D:\a\TrainStation\TrainStation\build\oss-eventstore\src\EventStore.Core\Cluster\EventStoreClusterClient.Elections.cs:line 105
--- End of inner exception stack trace ---
[12464, 1,11:34:12.622,FTL] Host terminated unexpectedly.
System.Exception: Invalid format for gossip seed port: :1]:2114
at EventStore.Core.ClusterVNodeOptions.ParseGossipEndPoint(String val) in D:\a\TrainStation\TrainStation\build\oss-eventstore\src\EventStore.Core\ClusterVNodeOptions.Framework.cs:line 70
Untested but for sure have to check, DNS Discovery with IPv6
There are scenarios where IPv6 is not working as expected, we should look into supporting it so the server doesn't generate errors or invalid configurations.
This investigation into IPv6 got triggered by: #4036
Some tested scenario's and their current results:
Single Node
Minimal secure configuration with any IP and:
Config:
Curl:
Returns invalid gossip:
Minimal secure configuration with specific IP:
Config:
Curl:
Looks like it's working.
Cluster
Specific IP & gossip with IP:
Config:
Error:
Specific IP & gossip with hostname:
Config:
On follower:
Any IP & gossip with hostname
Config:
Error:
Localhost & gossip with hostname
Config:
Error:
Localhost & gossip with ip
Config:
Error:
Untested but for sure have to check, DNS Discovery with IPv6
DB-490
The text was updated successfully, but these errors were encountered: