You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the 3000 port is open from the 127.0.0.1 interface
sam@block:~$ nmap 127.0.0.1 -p 3000
Starting Nmap 7.80 ( https://nmap.org ) at 2020-09-28 10:37 UTC
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00013s latency).
PORT STATE SERVICE
3000/tcp open ppp
Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
but not from the outside (which make the registration step fail)
sam@block:~$ nmap <my-domain> -p 3000
Starting Nmap 7.80 ( https://nmap.org ) at 2020-09-28 10:39 UTC
Nmap scan report for <my-domain> (<my-ip>)
Host is up (0.000074s latency).
PORT STATE SERVICE
3000/tcp closed ppp
Nmap done: 1 IP address (1 host up) scanned in 0.04 seconds
The docker network part seems right (I tried to run a simple http server) with the following and it works:
docker run --name python_simplehttpserver -d -v /home/foo:/var/www:ro -p 80:8080 trinitronx/python-simplehttpserver
I also checked if my public ip was correctly resolved by ./scripts/function/get_public_ip and yes, it's the case. Any idea of what may be wrong here?
The text was updated successfully, but these errors were encountered:
Sorry for the slow response. I tend to forget to check the issues.
Make sure your HOST_ADDR environment variable is correct. It should match the IP of the node. Otherwise just set it to HOST_ADDR=0.0.0.0, then it will not depend on if you set it to the correct IP.
When starting the relay with the following commands (like in the readme):
the 3000 port is open from the 127.0.0.1 interface
but not from the outside (which make the registration step fail)
The docker network part seems right (I tried to run a simple http server) with the following and it works:
I also checked if my public ip was correctly resolved by ./scripts/function/get_public_ip and yes, it's the case. Any idea of what may be wrong here?
The text was updated successfully, but these errors were encountered: