Skip to content
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

grpc: ClientConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp: address too many colons in address #69

Open
EasonWang01 opened this issue Feb 24, 2017 · 2 comments

Comments

@EasonWang01
Copy link

when I follow this tutorial https://github.com/IBM-Blockchain/learn-chaincode

to deploy

./start will cause [shim] CRIT : peer.address not configured, can't connect to peer

so I change to

 CORE_CHAINCODE_ID_NAME=mycc CORE_PEER_ADDRESS=https://7f10092d31a54fd6a75a158a6e61044e-vp0.us.blockchain.ibm.com:5003 ./start

but also some error

 grpc: ClientConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp: address https://7f10092d31a54fd6a75a158a6e61044e-vp0.us.blockchain.ibm.com:5003: too many colons in address"; Reconnecting to "https://7f10092d31a54fd6a75a158a6e61044e-vp0.us.blockchain.ibm.com:5003"


@EasonWang01 EasonWang01 changed the title grpc: ClientConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp: address https://7f10092d31a54fd6a75a158a6e61044e-vp0.us.blockchain.ibm.com:5003: too many colons in address grpc: ClientConn.resetTransport failed to create client transport: connection error: desc = "transport: dial tcp: address too many colons in address Feb 24, 2017
@masterDev1985
Copy link
Contributor

@EasonWang01 If you are trying to build and run chaincode in dev mode, connecting it to peer, you should use the grpcs url to connect to the peer. Also, It sounds like you need to put brackets around the hostname. See this issue on stack overflow:

http://stackoverflow.com/questions/8854682/go-json-rpc-too-many-colons

And the relevant golang code (search for your error message):

https://golang.org/src/net/ipsock.go

@Katiyman
Copy link

Katiyman commented Aug 1, 2017

Was this resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants