ssl3_get_record error while accessing Dockerized Node via PRC

[chia-network]

ssl3_get_record error while accessing Dockerized Node via PRC

[ohld]

This is the full output of curl -v with increased verbosity:

*   Trying 0.0.0.0:8555...
* TCP_NODELAY set
* Connected to 0.0.0.0 (127.0.0.1) port 8555 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/certs/ca-certificates.crt
  CApath: /etc/ssl/certs
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* error:1408F10B:SSL routines:ssl3_get_record:wrong version number
* Closing connection 0
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong version number

[epaypool-admin]

Try to put in entrypoint.sh

sed -i 's/localhost/127.0.0.1/g' ~/.chia/mainnet/config/config.yaml
# allow for port forward using cloudflare of full node
sed -i 's/self_hostname: 127.0.0.1/self_hostname: 0.0.0.0/g' ~/.chia/mainnet/config/config.yaml

[ohld]

@epaypool-admin no, same result. 😔

[ohld]

Just found out that the cause of this problem was running nginx who listened to 8555 and 8444 ports. I disabled it and everything worked fine: I can successfully query the dockerized node from outside of the container.

But I really want to route traffic using nginx (I'm using heroku-style opensource PaaS called Dokku, and nginx is built-in there). Well, at least I define there the problem is.

[luis360]

Just found out that the cause of this problem was running nginx who listened to 8555 and 8444 ports. I disabled it and everything worked fine: I can successfully query the dockerized node from outside of the container.

But I really want to route traffic using nginx (I'm using heroku-style opensource PaaS called Dokku, and nginx is built-in there). Well, at least I define there the problem is.

I am also considering using nginx proxy, how is nginx configured.