Not able to make public rpc calls on aleph-nodes
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- docker, kubernetes
- Domain
- infrastructure, networking
Research direction
Start with scripts/run_nodes.sh and compare its defaults with the Docker and Kubernetes deployment configuration described in the issue. Reproduce the difference between localhost access and the public wss:// endpoint, then verify that the RPC service is externally reachable through the deployed node.
Written by the indexing model from the issue text.
Description
Did you read the documentation and guides?
- I have inspected the documentation.
Is there an existing issue?
- I have searched the existing issues.
Description of the problem
As per instructions I have aleph-node running(by running scripts/run_nodes.sh), it is accessible through local host but on deployment to docker /kubernetes I am not able to connect to network through rpc url. (Example: wss://node.mynetwork.in) Is there any flag missing while running the node so that I can access it publically?
Information on your setup.
- Running on testnet or mainnet? - Running on a server on digital ocean (scripts/run_nodes.sh).
- Version of aleph-node - Cloned the repo from github(aleph-node)
- How do you run aleph-node - directly, docker, aleph-node-runner? - Docker
- s it a validator node or RPC-node? Full Node(6 running)
- what flags do you run aleph-node with - Default values from run script
- operating system - Unix
Steps to reproduce
No response
Did you attach relevant logs?
- I have attached logs (if relevant).
- Dominant language
- No language data
- Stars
- 2
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Cardinal-Cryptography/aleph-node-issues
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Cardinal-Cryptography/aleph-node-issues#17 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Cardinal-Cryptography/aleph-node-issues#14 · 5 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Cardinal-Cryptography/aleph-node-issues#13 · 4 comments ·
All issues in Cardinal-Cryptography/aleph-node-issues
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Mintplex-Labs/anything-llm#6490 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
HL7/fhir-ig-publisher#1375 ·
-
[quality] workflow-scripts guard reads test:unit:coverage as skipping the unit suite, blocking #632 Openagent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100