RPC enpoint not accessible outside docker #123

New issue

Closed

opened 2021-06-01 11:24:19 +00:00 by kake · 8 comments

kake commented

2021-06-01 11:24:19 +00:00

(Migrated from gitlab.com)

I am running a node with docker. When I attempt to talk to the RPC endpoint, I am getting connection refused error.
The same issue is observed with another witness node running with docker.

I have used Python-Peerplays to talk to the RPC endpoint. Python Peeraplays talks well to other nodes running same chain and other test nets.

I am running a node with docker. When I attempt to talk to the RPC endpoint, I am getting connection refused error. The same issue is observed with another witness node running with docker. I have used Python-Peerplays to talk to the RPC endpoint. Python Peeraplays talks well to other nodes running same chain and other test nets.

kake commented

2021-06-01 11:24:19 +00:00

(Migrated from gitlab.com)

assigned to @RoshanSyed

kake commented

2021-06-01 11:24:40 +00:00

(Migrated from gitlab.com)

made the issue confidential

RoshanSyed commented

2021-06-01 12:19:48 +00:00

(Migrated from gitlab.com)

@kake can you provide steps to reproduce? How you are running the image, which image are you trying to run, how are you trying to access the RPC endpoint? etc...

kake commented

2021-06-01 12:59:56 +00:00

(Migrated from gitlab.com)

Install and start peerplays with docker instance of peerplays
Start the node
Start BOS instance point to the running node.

BOS fails with the message, Number retries exceeded

1. Install and start peerplays with docker instance of peerplays 2. Start the node 3. Start BOS instance point to the running node. BOS fails with the message, Number retries exceeded

kake commented

2021-06-02 08:02:47 +00:00

(Migrated from gitlab.com)

The solution to the issue is to enable advanced options for port numbers to expose to the internet. An example is given below

 # Comma separated port numbers to expose to the internet (binds to 0.0.0.0)
 28 # PORTS=9777
 29 # Advanced Usage Example: 
 30 #
 31 #   Expose 9777 to the internet, but only expose RPC ports 8090 and 8091 onto 127.0.0.1 (localhost)
 32 #   allowing the host machine access to the container's RPC ports via 127.0.0.1:8090 and 127.0.0.1:8091
 33 #
 34 PORTS=9777,127.0.0.1:8090:8090,127.0.0.1:8091:8091

The solution to the issue is to enable advanced options for port numbers to expose to the internet. An example is given below ``` # Comma separated port numbers to expose to the internet (binds to 0.0.0.0) 28 # PORTS=9777 29 # Advanced Usage Example: 30 # 31 # Expose 9777 to the internet, but only expose RPC ports 8090 and 8091 onto 127.0.0.1 (localhost) 32 # allowing the host machine access to the container's RPC ports via 127.0.0.1:8090 and 127.0.0.1:8091 33 # 34 PORTS=9777,127.0.0.1:8090:8090,127.0.0.1:8091:8091 ```

kake (Migrated from gitlab.com) closed this issue

2021-06-02 08:03:01 +00:00

bobinson commented

2021-06-03 04:40:43 +00:00

(Migrated from gitlab.com)

mentioned in commit 7d1db4e883

mentioned in commit 7d1db4e88387bd87037888cb2f8d6d063bcfdd19

bobinson commented

2021-06-03 04:40:43 +00:00

(Migrated from gitlab.com)

mentioned in commit 890079c33f

mentioned in commit 890079c33f605f6408d3c8cdaf433bfff56cb005