Problem is in the topic.
The website is not reachable over .onion, so I want to visit it normally. Not possible, because the browser redirects me to the .onion service, even tough I specifically disabled that in the settings.
How can I force the browser to visit the website I put on the URL bar, and not switch it for something else?
You can find the article here: https://github.com/databurn-in/PeerLink
If you go to certain clearnet sites in the Tor browser, namely ProtonMail.com, you will receive a notification from your browser that a .onion version of the site is available. You're also able to adjust a setting in your browser to always prefer the .onion version, when available.
The way Tor knows to inform you of a .onion service is that website owners can add a "Onion-Location" to their http headers with the relevant onion address.
I've added the appropriate headers to my nginx configureation and when I test it via
wget --server-response --spider clearnet-site.com
I see:
Onion-Location: http://notactuallymyonionsitehereuqp4whpvqq37crihkvupxyb4aofnzd.onion/
So it should work, awesome! But when I browse my site in the Tor browser I do not get a notification of a .onion version being available despite the header being read by the server.
Any idea why? I checked both the https and http version of the clearnet site via the tor browser and it doesn't seem to take note of the onion service. If I go to protonmail.com, it'll detect it and notify me.
update
I got it working but only by using the html meta tag (below).
<meta http-equiv="onion-location" content="http://<your-onion-service-address>.onion" />
Not sure why the nginx config didn't work, since it's detected when you check the headers. But now the https version of the clearnet site will redirect automatically to the onion version OR ask you if you'd like to switch to the .onion, based on your settings in your Tor Browser. Neat.
We're proud to announce that LocalMonero is now available as a Tor single onion service at this address: http://localmonerogt7be.onion!
As far as we know we are the only cryptocurrency-related service to implement Tor single onion. The Monero community will appreciate this more than most.
An extra feature of our Tor service as compared to our clearnet service is that it doesn't have any Google Analytics! We're sure this will make a lot of you very happy.
###What's single onion?
Onion services are great because they offer both anonymity on the service and the client side.
An onion service connection between a client and a service goes through 6 hops, while a regular connection with Tor is 3 hops. Onion services are much slower than regular Tor connections because of this. Here's a graph illustrating this process.
However, there are cases where the onion service does not require anonymity. The main example of this is when the service provider does not need to hide the location of its servers. This is an issue that Facebook brought to the Tor project and as a result of their collaboration they have developed single onion.
With single onion, a service specifies that it does not need anonymity, thus cutting the 3 hops between the service and its Rendezvous Point and speeding up the connection while keeping the client anonymous. Here's a single onion graph.
We thank you for your continued support and we will keep implementing more cypherpunk features as time goes on.
EDIT: LocalMonero is now available on I2P!
• I2P domain: lm.i2p
• B32 I2P domain: yeyar743vuwmm6fpgf3x6bzmj7fxb5uxhuoxx4ea76wqssdi4f3q.b32.i2p
We're proud to announce that LocalMonero is now available as a Tor single onion service at this address: http://lclmnroewgycudgz.onion!
As far as we know we are the only cryptocurrency-related service to implement Tor single onion. The Monero community will appreciate this more than most.
An extra feature of our Tor service as compared to our clearnet service is that it doesn't have any Google Analytics! We're sure this will make a lot of you very happy.
###What's single onion?
Onion services are great because they offer both anonymity on the service and the client side.
An onion service connection between a client and a service goes through 6 hops, while a regular connection with Tor is 3 hops. Onion services are much slower than regular Tor connections because of this. Here's a graph illustrating this process.
However, there are cases where the onion service does not require anonymity. The main example of this is when the service provider does not need to hide the location of its servers. This is an issue that Facebook brought to the Tor project and as a result of their collaboration they have developed single onion.
With single onion, a service specifies that it does not need anonymity, thus cutting the 3 hops between the service and its Rendezvous Point and speeding up the connection while keeping the client anonymous. Here's a single onion graph.
We thank you for your continued support and we will keep implementing more cypherpunk features as time goes on.
