Skip to content
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

Update hostname and IP address of BTC node lva54pnbq2nsmjyr.onion #4174

Merged
merged 1 commit into from Apr 20, 2020

Conversation

devinbileck
Copy link
Member

I deployed a new instance and as a result have a new IP address.
Also, while I was at it I added it to my bisq.services domain.

I deployed a new instance and as a result have a new IP address. Also,
while I was at it I added it to my bisq.services domain.
@ripcurlx
Copy link
Member

I deployed a new instance and as a result have a new IP address.

So I guess this means I should filter out your current IP address, right?

@devinbileck
Copy link
Member Author

Sure. I guess for those that don't use tor?

@ripcurlx
Copy link
Member

Sure. I guess for those that don't use tor?

Yes, I just filtered 165.227.34.198:8333, btc1.dnsalias.net:8333

Copy link
Member

@ripcurlx ripcurlx left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK - Checked IP on https://bitnodes.io and everything 172.105.21.216:8333 /Satoshi:0.19.1/ seems to be fine.

@ripcurlx ripcurlx merged commit 590f16d into bisq-network:master Apr 20, 2020
@ripcurlx
Copy link
Member

@devinbileck Please also ping @wiz in that case that he can update his alert script. Thanks!

@devinbileck devinbileck deleted the update-btc-node branch April 20, 2020 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants