@logicalpath @yogk I assume both of your incoming traffic is blocked. So the TCP listener was created and it is listening - like @yogk indicates above - but cannot receive data. Please check your firewall settings whether the incoming traffic on port 8905 is allowed. I will do some work ASAP on this, so when there is no incoming traffic allowed then we will make that clear for user. The route of the problem is how RPC works. Via the RPC module you can send out data which explains why could you publish your data, but the receive of the reply is already blocked. We need to do more work on handling these scenarios and informing users about the errors via the UI. When the port is opened, the firewall is sorted out then Streembit seems works OK, but when there are some errors the situation is confusing. @logicalpath please email me your log file.
@yogk This tool at http://www.yougetsignal.com/tools/open-ports/ should display "Port 8905 is open on xxx.xxx.xxx.xxx" the x is your Ip Address
port 8905 is blocked
Im going to do port forwarding next
I dont see where the port is acutally blocked
in the router/cable modem
with the tool http://www.yougetsignal.com/tools/open-ports/,
i get "Port 8905 is closed on 1xx.5.1xx.3". I will have to now check how can i open this port 8905. But even the standard http tcp port 80 also shows as closed, then how can i receive web data if its closed.
i get "Port 8905 is closed on 1xx.5.1xx.3". I will have to now check how can i open this port 8905. But even the standard http tcp port 80 also shows as closed, then how can i receive web data if its closed.
@yogk You can receive data over the HTTP protocol in your browser because the browser app sends data to the listening port in the web server as a TCP client, and then it receives the message back on the very same socket. So that is a send-receive topology on the TCP client socket. In order to receive data over the HTTP protocol (browser) you don't need a TCP listener, but you use a TCP client. (See my post and proposal about the WS problem in the Google group, which describes how to use such TCP client). So to get web data in your browser you never open a listening port. So don't be confused from that TCP client and TCP listener sockets are different things. For a P2P application you need a TCP listener socket. What you wrote clearly indicates that your TCP listener is not operational. I suggested this could be the issue. If you forward your port on your router then the Streembit client will be reachable by other peers. Thanks for trying :-) let us know if you need anymore help.
Here is a blog I wrote with some port forwarding tips. Hope this helps https://deardolphinblog.wordpress.com/2016/07/05/port-forwarding-tips/ @yogk
Information in README is confusing and inaccurate
Thanks a lot!
I think this infor should be added to the official
README.md
Hello All, I am trying to run the source code of https://github.com/streembit/streembitui on window machine . can you please give me some instructions how to run on it?
