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

RPC connectivity issue #3348

Closed
blockchain-app12 opened this issue Jan 29, 2022 · 5 comments
Closed

RPC connectivity issue #3348

blockchain-app12 opened this issue Jan 29, 2022 · 5 comments
Assignees
Labels
dev experience The build system, things that enable easier development etc.

Comments

@blockchain-app12
Copy link

I running the besu node setup in private chain. Totally 4 nodes.
1 node is master node and others are peer nodes.
Then none of the RPC method was not working while we trying to get response.
Kindly let me know the solution for the issue to resolve this.

image

@garyschulte garyschulte added the dev experience The build system, things that enable easier development etc. label Feb 1, 2022
@macfarla
Copy link
Contributor

macfarla commented Feb 3, 2022

👋 @osiz-blockchainapp - can you tell us a bit more about your besu setup - can you share your besu config file as well as version info:

Versions (Add all that apply)

  • Software version: [besu --version]
  • Java version: [java -version]
  • OS Name & Version: [cat /etc/*release]
  • Kernel Version: [uname -a]
  • Virtual Machine software & version: [vmware -v]
  • Docker Version: [docker version]
  • Cloud VM, type, size: [Amazon Web Services I3-large]

@macfarla macfarla self-assigned this Feb 3, 2022
@blockchain-app12
Copy link
Author

wave @osiz-blockchainapp - can you tell us a bit more about your besu setup - can you share your besu config file as well as version info:

Versions (Add all that apply)

* Software version: [`besu --version`]

* Java version: [`java -version`]

* OS Name & Version: [`cat /etc/*release`]

* Kernel Version: [`uname -a`]

* Virtual Machine software & version: [`vmware -v`]

* Docker Version: [`docker version`]

* Cloud VM, type, size: [Amazon Web Services I3-large]

Hi,
Followed this link: https://besu.hyperledger.org/en/stable/Tutorials/Private-Network/Create-IBFT-Network/

Versions:
Besu: besu/v21.1.4/linux-x86_64/openjdk-java-11
Java: openjdk version "11.0.13"
OS & Version: Ubuntu & 20.04.3 LTS (Focal Fossa)
Kernal version: 5.11.0-1020-aws #21~20.04.2-Ubuntu x86_64 x86_64 x86_64 GNU/Linux
VM: No
Docker: No
Cloud Vm, type, size: AWS, 150GB

@macfarla
Copy link
Contributor

macfarla commented Feb 7, 2022

Since you're trying to access a machine on AWS, I'm guessing the issue is in allowing that request in and out. By default, Besu accepts traffic from localhost/127.0.0.1 only. https://besu.hyperledger.org/en/stable/Reference/CLI/CLI-Syntax/#host-allowlist

  • can you set host-allowlist=["*"] and retry
  • if that works, then change ["*"] to the list of client IPs that you want to allow
  • if you still get the same error, can you verify that executing the curl request from the same host can work ie accessing via localhost

@macfarla
Copy link
Contributor

Hi @osiz-blockchainapp - are you still having issues with this?

@MadelineMurray
Copy link
Contributor

hi @osiz-blockchainapp - we're closing this one. If you're having issues in the future, please reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev experience The build system, things that enable easier development etc.
Projects
None yet
Development

No branches or pull requests

4 participants