Closed GrantJMiles closed 10 months ago
Hi @GrantJMiles, when using esdb+discovery it looks like the endpoints appear in ConnectivitySetttings.DnsGossipSeeds rather than Address, so hopefully it is connecting to the correct endpoint.
That doesn't help you with your error though. are you using windows 7 by any chance?
I can see the values are being set in DnsGissipSettings. I am developing on an Ubuntu 22.04 machine using the net 7 remote container (with 8 rc1 manually installed).
Do I need to do something to the configuration of ES to enable HTTP/2
Proxy issue!
:+1:
Describe the bug When following the simple guide on the event store docs to create a client I am getting persistent errors when trying to
AppendToStreamAsync
with the error below:On inspection of the settings that get created it would seem that the connection string is not being parsed correctly
To Reproduce Steps to reproduce the behaviour:
Expected behaviour I would expect to be able to see the host that I am actually targeting, not the default localhost settings
Actual behavior An object that is remarkable similar to what is created when calling
EventStoreClientSettings.Default
EventStore details
Event Store is being run in docker alongside my remote development container definition
volumes: eventstore-volume-data: eventstore-volume-logs: