-
Notifications
You must be signed in to change notification settings - Fork 670
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
testnet.programmingbitcoin.com is down #151
Comments
I suspect he's just RPC'ing to his own full node. It might be nice for the next edition for Jimmy to show readers how to setup a full node (pretty easy now using Docker) and RPC to it. |
@steelsparrow I used blockstream API and it works fine
|
@chanhosuh I'm currently in chapter 10 where you need to make a network handshake with testnet.programmingbitcoin.com but I guess the server is still down do you think I need a local full node to test this ? |
@MichelKansou you can find someone's node to connect to, but in the end, you'll just be spamming them (especially if you aren't doing the handshake correctly!), so it's better to just run your own node. I think it's probably also more useful as a developer to run your own node anyway. It's not difficult to run a local node using Docker, exposing ports 8333 / 18333. Then connect a socket to localhost:8333 (or 18333) by initializing You can use this docker setup: https://github.com/chanhosuh/docker-bitcoin |
@chanhosuh thank you I already have a full node running so I will use it 😁 |
@chanhosuh yesterday I was trying to use my remote full node but I'm getting a RuntimeError |
@chanhosuh I just found out I needed to configure my router to enable 8333 Port Forwarding and also add |
Hi guys, I noticed that the |
I've been trying to get a alternative testnet going for the last week. finally got a testnet node running in docker. How do I access it and substitute it in get_urls? like this Is not accessible in a browser but don't know if it should be this is what docker container inspect says my exposed ports are
any help appreciated |
Port IIRC, at the least the one exercise was to communicate according to the P2P protocol |
Thanks @marcdk I'm clear on the port to use. I'm more asking how to use it. specifically for the last exercise Chapter12 exercise 6. It connects with
which doesn't work changing to
gives me the below get address error which is why I'm trying to connect to my own testnet node
I'm also getting this from my docker so I don't think the port is being exposed properly
appreciate any help |
Just a couple of things from my understanding that can hopefully help:
Hope this helps |
Would you still have this code? I've been trying everything I found to fix this but couldn't. The link you shared is not working anymore. Tkws |
Hi @GKenu, I've just had a look, but I don't have the code anymore. Sorry about that! |
Hi Marc! I just managed to do it. I sent an email to Jimmy and he got his
server back up running - I managed to finish all exercises.
Thanks either way!
…On Tue, May 10, 2022 at 5:46 AM Marc ***@***.***> wrote:
Hi @GKenu <https://github.com/GKenu>, I've just had a look, but I don't
have the code anymore. Sorry about that!
—
Reply to this email directly, view it on GitHub
<#151 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ATTYSDWB5X3TWQEHI3R4S6LVJIO6RANCNFSM4H2S7F6A>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I think the node is still down, I tried to connect from a new node but connection is not stable. Any indication of what can be wrong would be much appreciated. |
Like mainnet, the testnet block explorer appears to be down. Would it be possible for you to note the explorer you are running so users can bring up private instances to continue working through the exercises in the book?
The text was updated successfully, but these errors were encountered: