Bitcoin Forum
April 26, 2024, 01:10:12 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Running a Full Node through VPN?  (Read 1965 times)
Geremia (OP)
Sr. Member
****
Offline Offline

Activity: 502
Merit: 251


View Profile WWW
November 27, 2015, 04:33:21 AM
 #1

My ISP has blocked port 8333, due to the gigs of inbound traffic I incurred running a full node. Consequently, I would like to run a full node through VPN (specifically, OpenVPN with an OpenVPN provider).

Would I need to have the VPN forward port 8333?

(cf. the related Bitcoin StackExchange question)

BTC tip jar | my BTC wiki, BTC StackExchange | Tox ID: 65C3E8810738AD9D175234808FCB317A1103632903436203D45411AE97C03F54C34861AB6663
Join Kraken. | The best, free book on Bitcoin: Mastering Bitcoin
Nos cum prole pia benedicat Virgo Maria.
Even in the event that an attacker gains more than 50% of the network's computational power, only transactions sent by the attacker could be reversed or double-spent. The network would not be destroyed.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
Newar
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


https://gliph.me/hUF


View Profile
November 27, 2015, 05:27:44 AM
 #2


Yes, however you probably will find that somebody else will have forwarded 8333 already.

OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
achow101
Moderator
Legendary
*
Offline Offline

Activity: 3374
Merit: 6535


Just writing some code


View Profile WWW
November 27, 2015, 06:54:00 AM
 #3

You can just set your node to use a different port. Just change the port to something else and use that until your ISP blocks it and just keep switching it.

GriffinHeart
Full Member
***
Offline Offline

Activity: 182
Merit: 100


Hello there!


View Profile
November 27, 2015, 02:30:30 PM
 #4

Not through a program like Tor, but I'm sure it's doable.
Also, as the guy above me said, port 8333 will probably already be forwarded, if it isn't do it yerrself.

Hi there, I'm from South Africa.
This means I'm poor, I guess.
Geremia (OP)
Sr. Member
****
Offline Offline

Activity: 502
Merit: 251


View Profile WWW
November 27, 2015, 08:13:45 PM
 #5

Not through a program like Tor, but I'm sure it's doable.
Yes, I think you'd have to create a hidden service, I think it's called.

BTC tip jar | my BTC wiki, BTC StackExchange | Tox ID: 65C3E8810738AD9D175234808FCB317A1103632903436203D45411AE97C03F54C34861AB6663
Join Kraken. | The best, free book on Bitcoin: Mastering Bitcoin
Nos cum prole pia benedicat Virgo Maria.
BitAurum
Sr. Member
****
Offline Offline

Activity: 318
Merit: 250


View Profile
November 28, 2015, 09:02:20 AM
 #6

Not through a program like Tor, but I'm sure it's doable.
Yes, I think you'd have to create a hidden service, I think it's called.
You have to create a hidden service only if your using Tor. If your using a VPN your don't have to create a hidden service.
Newar
Legendary
*
Offline Offline

Activity: 1358
Merit: 1000


https://gliph.me/hUF


View Profile
December 05, 2015, 04:28:22 AM
 #7

You can just set your node to use a different port. Just change the port to something else and use that until your ISP blocks it and just keep switching it.

IIRC, different ports than 8333 are not recommended though for nodes, as other clients will look on 8333.

OTC rating | GPG keyid 1DC91318EE785FDE | Gliph: lightning bicycle tree music | Mycelium, a swift & secure Bitcoin client for Android | LocalBitcoins
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!