Bitcoin Forum
February 24, 2018, 03:09:33 PM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: RPi bitcoind not listening on port 8333  (Read 404 times)
mindrust
Legendary
*
Online Online

Activity: 980
Merit: 1025


Don't call my project BCASH you poor fucks!


View Profile WWW
July 11, 2017, 06:49:51 PM
 #1

Can someone tell me what's wrong with my Pi3/Full Node/Ports?



I used the command "netstat -a" and  the result is above. When I check my port 8333 on http://canyouseeme.org/ It is always closed. My ports are OPEN on my router. Both for PI and my Laptop. Separately. Because they have separate IP's. Router firewall is off.

The interesting thing is; when I run my full node on my laptop, 8333 becomes OPEN. When I close the node, It becomes CLOSED again. But whatever I do it with my Pi, It stays CLOSED as always.

What's wrong with my setup?

***I always have 8 connections on my PI3 and just a mintute ago I had 9 connections but I recently opened/closed my full node on my laptop so my ports became open for a short time.
***PI downloaded 325k blocks.
***My router has no uPnP support.

1519484973
Hero Member
*
Offline Offline

Posts: 1519484973

View Profile Personal Message (Offline)

Ignore
1519484973
Reply with quote  #2

1519484973
Report to moderator
1519484973
Hero Member
*
Offline Offline

Posts: 1519484973

View Profile Personal Message (Offline)

Ignore
1519484973
Reply with quote  #2

1519484973
Report to moderator
The money raised from these ads will be used to pay for improved forum software and other useful stuff.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1519484973
Hero Member
*
Offline Offline

Posts: 1519484973

View Profile Personal Message (Offline)

Ignore
1519484973
Reply with quote  #2

1519484973
Report to moderator
1519484973
Hero Member
*
Offline Offline

Posts: 1519484973

View Profile Personal Message (Offline)

Ignore
1519484973
Reply with quote  #2

1519484973
Report to moderator
1519484973
Hero Member
*
Offline Offline

Posts: 1519484973

View Profile Personal Message (Offline)

Ignore
1519484973
Reply with quote  #2

1519484973
Report to moderator
achow101
Moderator
Legendary
*
Offline Offline

Activity: 1316
Merit: 1151


3F1Y9yquzvY6RWvKbw2n2zeo9V5mvBhADU


View Profile WWW
July 11, 2017, 10:00:37 PM
 #2

Please do not hijack other people's threads with your own question/issue. Make a new thread instead. I have split your post into a new thread for you.



Check that your router is forwarding post 8333 to the right IP address. It sounds like it is set to forward port 8333 to your laptop's IP address, not your Raspberry Pi's. The router does not automagically know which IP address it should forward a port to, so you must tell it.

mindrust
Legendary
*
Online Online

Activity: 980
Merit: 1025


Don't call my project BCASH you poor fucks!


View Profile WWW
July 11, 2017, 10:44:03 PM
 #3

Please do not hijack other people's threads with your own question/issue. Make a new thread instead. I have split your post into a new thread for you.



Check that your router is forwarding post 8333 to the right IP address. It sounds like it is set to forward port 8333 to your laptop's IP address, not your Raspberry Pi's. The router does not automagically know which IP address it should forward a port to, so you must tell it.

I opened the ports for both devices separetely but I recently learned that it is not possible because the router may get confused if I do so. So I removed the Laptop's Ip from the forwarded ports list and left raspi there. Nothing has changed.

Maybe I should try a different port for pi now...

mindrust
Legendary
*
Online Online

Activity: 980
Merit: 1025


Don't call my project BCASH you poor fucks!


View Profile WWW
July 12, 2017, 07:32:06 AM
 #4

Update: The problem is solved.

I just had to remove every thing on my router, and re-setup the port forwarding for my Pi3. Leaving the old setup wasn't enough. Had to remove it first and make a clean setup.

My port is open now.

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!