search

OpenBazaar / OpenBazaar-Server

(Deprecated) OpenBazaar 1.0 Server daemon for communication with OpenBazaar-Client
MIT License
608 stars 173 forks source link

Server ports are only reachable from 127.0.0.1. Impossible to connect. #396

Open Nd60 opened 8 years ago

Nd60 commented 8 years ago

Server only listens on IP address 127.0.0.1. It does not listen on the external address. In my case this external IP address is 192.168.1.34. I have disabled UPnP on purpose on the router.

Operating System (OS and version): Ubuntu 14.04.4 LTS OpenBazaar version: openbazaar_1.1.4_amd64.deb Reproducible: Always

Command line on the machine where OpenBazaar is running: $ ifconfig eth0 eth0 Link encap:Ethernet HWaddr 28:d2:44:70:b2:ea
inet addr:192.168.1.34 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::2ad2:44ff:fe70:b2ea/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:397045 errors:0 dropped:0 overruns:0 frame:0 TX packets:309834 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:395705754 (395.7 MB) TX bytes:60007154 (60.0 MB)

$ sudo ufw allow 18469 Rule updated Rule updated (v6) $ telnet 127.0.0.1 18469 Trying 127.0.0.1... Connected to 127.0.0.1. Escape character is '^]'. ^]quit

telnet> quit Connection closed. $ telnet 192.168.1.34 18469 Trying 192.168.1.34... telnet: Unable to connect to remote host: Connection refused

Observed Behavior: Port 18469 is only reachable from 127.0.0.1. Port 18469 is not reachable from outside the machine where OpenBazaar is running.

Expected Behavior: It is necessary that port 18469 is reachable when accessing the eth0 interface. In this case, that is IP address 192.168.1.34

Nd60 commented 8 years ago

$ netstat -an | grep 18469 tcp 0 0 127.0.0.1:18469 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:18469 127.0.0.1:57425 ESTABLISHED tcp 0 0 127.0.0.1:57425 127.0.0.1:18469 ESTABLISHED

cpacia commented 8 years ago

Right now it doesn't listen on the local IP. Probably wont be able to do that until we switch to the go version.

Nd60 commented 8 years ago

Does that mean that my store will be invisible to clients if I don't activate UPnP?

cpacia commented 8 years ago

Your store should be visible to everyone outside your local network. If you have another computer on the same wifi it might not be able to connect but that's it.

Nd60 commented 8 years ago

On https://www.reddit.com/r/OpenBazaar/comments/4emv1j/openbazaar_troubleshooting_thread/ , it is said: "Most users shouldn't need port forwarding, but if you have problems seeing others or others cannot see your page, you can try opening the following ports": 18466/TCP, 18467/UDP, 18469/TCP, 18470/TCP.

However, what is the point of doing port forwarding if the OpenBazaar server is not reachable from the router?

Bezpol commented 8 years ago

I have problem on the same Ubuntu and OpenBazaar version: openbazaar_1.1.5_amd64.deb my client openbazaar starting server but can't connect to default (localhost). I think that is the same problem with listing ports of openbazaar server. Could you help us ?

MidnightLightning commented 7 years ago

I believe I'm encountering something similar trying to get my server to be visible to my own home network. I have a CoreOS box that I'm attempting to run a Docker-ized OpenBazaar server daemon in. The logs from the Docker container show it starts up well, and seems to be able to connect to the OpenBazaar network (outbound requests from the Docker container work), but there is a UPnP error upon startup, and I can't get any of my own local clients (telnet ping on the CoreOS box itself, and the desktop client on my own workstation in the same WiFi range) to connect to the Dockerized application, even though the Docker version has ports mapped and should be accessible. Is the solution to this just wait for the go version and jump to that version?