-
Notifications
You must be signed in to change notification settings - Fork 519
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
New: Tor2IP (ip2tor) Bridge Subscriptions #1194
Comments
To create a subscription script its needed to easily parse JSON data from such a shop. This may get complicated with bash .. so I looked at python and to make user interaction using the following UI dialogs: http://pythondialog.sourceforge.net This python dialog wrapper can be installed from the debian repos with: |
Consider a new config valaue format for storing the list of subscription to bridges - see: #1185 |
I noticed yesterday that a key part was missing in the API.. but now this workflow should work:
|
Extending is slightly different (shorter) steps:
|
I included many/most of the data in the nested relations. So after |
TODO: after RC1 release change default shop to production server |
|
@frennkie let me know when you have time to setup the IP2TOR store |
In the context of the IP2Tor bridges the HTTP (typically port 80) to HTTPS (typically port 443) would not work that easily. Normally nginx just changes the port from 80 to 443.. but with the bridges neither HTTP will have 80 nor HTTPS will have 443.
My feeling is that it's ok, that we have 80 and 443 on the same .onion.
Not yet... I'd be happy for any help on this. I think doing an "inspection" of flowing data borders on evil. But the |
@frennkie I added more details in case that a IP2TOR order is not working. Here is an example ao an oder that was payed but then timed out ... let me know if this is good enough for debug:
|
@grnqrtr from "aws1" and the pruchase date I can look your subscription up in the database. As far as I see it you set up this subscription to port 80. Are you using this IP2TOR bridge for HTTP or HTTPS connections? If you are using cleartext HTTP then the next renew should fail as I merged a change into the backend that rejects if you don't use encrypted HTTPS traffic. Would be great if you could give some feedback. |
I set it up to be able to access BTCPayServer over clearnet. I actually want it to be for HTTPS, but when I go to it in browser it's not secure. I'm not exactly sure how to specify that. I thought maybe having the Let's Encrypt Client enabled from EDIT: I'm happy to test & give more feedback. If this isn't the place to go back and forth over my HTTPS issue, feel free to contact me on Telegram or Keybase instead (same username, grnqrtr). |
@grnqrtr v1.6 RC3 will give you more details on the IP2TOR in the mainmenu for BTCPay. |
@frennkie trying to order a bridge I got the following timeout:
|
Autossh ist still not working for me... I have to change the - M 0 to - M 20000 every time and forgot after upgrading to RC3. Invoices should work again. |
@frennkie should we change something in the
|
I'm wondering whether I am the only person using this or if I misconfigured something on the sshd side. I would say the safest thing would be that we stick with the default (-M 0) but allow for customization via raspiblitz.conf. |
@frennkie can you open a seperate issue for that - marked for v1.7? |
Done.... I'm in parallel working on Django-IP2Tor to implement a heartbeat from the Hosts and a alive check for the Lightning Nodes.. Makes no sense to list stale hosts or hosts for which no LND backend is available to create invoices. |
After getting my other issues figured out, I got back to testing this again and just wanted to report that my new ip2tor bridge subscription for BTCPay is up and running fine with the Let's Encrypt subscription. Things are working well, very cool! Just thought I'd mention one thing, after seeing this screen it took probably 5~10 minutes before I could access the new bridge: I almost cancelled the subscription and was going to try with the other option |
From the server logs I have:
Systemd: So it should not have taken more than one minute to be available. |
I don't know, maybe it was something on my end then. I kept refreshing the page, but didn't come up for a while. |
OK tested again and making a subscription is still working. Closing this issue for v1.6.1 release. |
As part of the Lightning Hackathons a tor2ip bdrige concept was developed to make it easy for a RaspiBlitz running behind TOR to buy a tunnel bridge giving it a clearnet IP+port to make services like the REST API reachable for Mobile Apps, POS systems or other apps.
The goal if this issue is to make it possible to make a subscription to a automated shop offering such bridges - running the open shop software: https://github.com/frennkie/django-ip2tor
The text was updated successfully, but these errors were encountered: