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

How can I enable REST api service in hyperledger fabric 1.0 preview environment? #12

Closed
allegewhd opened this issue Feb 2, 2017 · 15 comments
Labels

Comments

@allegewhd
Copy link

allegewhd commented Feb 2, 2017

Hi, yeasy, thanks for the great job of this project.I followed hyperledger/1.0/README.md, and run go/chaincode_example02 by peer command successfully. But when I tried to access some REST api endpoint, orderer service always refused those http connection immediately.

transport: http2Server.HandleStreams received bogus greeting from client: .....

I am wondering how can share fabric-ca enroll session with peer proccess, sounds like fabric-ca server listenning port 8888, but peer server proccess do not communicate with this port. Is the reason that v1.0 is still on developing, integration part is not implemented yet?

@yeasy
Copy link
Owner

yeasy commented Feb 5, 2017

hi, in fabric peers, the rest api will be deprecated, and only support grpc connection.
for fabric-ca, the port 8888 is actually from the cfssl. Recently the grpc port is updated to 7054.

@rezwan
Copy link

rezwan commented Feb 6, 2017

from my website i want to invoke,deploy or query. In my case if rest call doesnt work how can I communicate with chain code ? any example will be appreciated.

@yeasy
Copy link
Owner

yeasy commented Feb 8, 2017

You have to use the client or SDK.

See http://hyperledger-fabric.readthedocs.io/en/latest/gettingstarted/

@allegewhd
Copy link
Author

Thanks yeasy, I'll try some SDK samples. But still wondering how to integrate fabric-ca with orderer and peer process just like member service in v0.6. Hope that hyperledger_code_fabric project will be helpful:)

@allegewhd allegewhd changed the title How can enable REST api service on hyperledger fabric 1.0 preview environment? How can I enable REST api service in hyperledger fabric 1.0 preview environment? Feb 8, 2017
@yeasy yeasy added the question label Feb 9, 2017
@rezwan
Copy link

rezwan commented Feb 19, 2017

Thanks a lot. The upper link works perfectly in CLI mode. I followed all the instruction but when I call "node deploy.js" command it returns error from hackfest/node_modules/elliptic/lib/elliptic/ec/index.js file line 94:key = this.keyProfomPrivate(key,enc) returns null . May be this is because of certificate related error. What could be the reason....

@yeasy
Copy link
Owner

yeasy commented Feb 20, 2017

suggest u post the problem to the node sdk channel.

chat.hyperledger.org

@rezwan
Copy link

rezwan commented Feb 20, 2017

Yes I will try to find solution from there. Thanks

@yeasy yeasy closed this as completed Feb 21, 2017
@nbkesavan
Copy link

Hi Yeasy,
Did you got any solution regarding the REST API .

@yeasy
Copy link
Owner

yeasy commented May 30, 2017

No, in 1.0, we do not support rest api feature.

@nbkesavan
Copy link

Thanks Year.
Is there any other alternate API to communicate with peer from web application

@yeasy
Copy link
Owner

yeasy commented May 31, 2017

The sdk is the only way.

See https://wiki.hyperledger.org/projects/cello, which can work with sdk-py together.

@kmohanar
Copy link

Should we use only py or can we use other SDKs from go, java, node.

@yeasy
Copy link
Owner

yeasy commented Jun 1, 2017

@kmohanar certainly depends on the application language.

@kmohanar
Copy link

kmohanar commented Jun 2, 2017

Is there any technical document/steps which explain how to make cello and sdk-py together to interact with the yeasy docker images. If so, Please share with us.

If there is any other SDKs support to interact with fabric also fine.

@archimonde1581
Copy link

When i test a gateway for baas platform ,it gives me a error message that :'no channel peers configured for channel'

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

No branches or pull requests

6 participants