Error accessing port publicly

jeremyccrane

PRO

a year ago

I am attempting to setup a new Layer-1 blockchain with three initial nodes on Railway. I can get the nodes running fine, and mining (proof-of-work) but cannot publicly access the apps via <url>:<port>.Dockerfile

EXPOSE 8541

Entrypoint Fileexec geth --datadir /app/data --http.port 8541Environment Variables

PORT=8541

Logs showing ports are open on app startupHTTP server started endpoint=127.0.0.1:8541 auth=false prefix= cors=* vhosts=*

Railway.yml

services:
  go-marscredit:
    build: .
    ports:
      - "8541:8541"
      - "8544:8544"

When I run telnet node1.marscredit.xyz 8541 I get an unable to connect to remote host error.

Is there something with my configuration that I am doing incorrectly?

Solved

5 Replies

brody

EMPLOYEE

a year ago

You may be setting the PORT to 8541 but that is only telling Railway what internal port to map to the external port 443.

Status changed to Solved railway • about 1 year ago

jeremyccrane

PRO

a year ago

Great. To make sure I understand, any port mapping that happens inside Railway containers all map to the public port of 443?

brody

EMPLOYEE

a year ago

I wouldn't say all, There can only be one internal http port that maps to the external https port 443.

jeremyccrane

PRO

a year ago

Copy, does this include the new proxy? I thought I saw somewhere the ability to access multiple ports publicly.

brody

EMPLOYEE

a year ago

The new proxy does not have support for multiple ports at this time.