Custom port support

[boldsuck]

Hi @theAkito, first of all thank you for the support of Tor hidden services.

Similar to manimaran website-monitor issue 4 But this time it's not because of the http <-> https protocol.

I've successfully tested with duckduckgo (http & https):
https://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/
http://duckduckgogg42xjoc72x3sjasowoarfbgcmvfimaftt6twagswzczad.onion/

My pages with custom port do not work:

• http://6dsdenp6vjkvqzy4wzsnzn6wixkdzihx3khiumyzieauxuxslmcaeiad.onion:18081/get_info
  = http://xmr-de-1.boldsuck.org:18081/get_info
• http://ip4zpbps7unk6xhlanqtw24f75akfbl3upeckfjqjks7ftfnk4i73oid.onion:18081/get_info
  = http://xmr-de-2.boldsuck.org:18081/get_info
• http://ct36dsbe3oubpbebpxmiqz4uqk6zb6nhmkhoekileo4fts23rvuse2qd.onion:38081/get_info
  = http://xmr-lux.boldsuck.org:38081/get_info

[theAkito]

Greetings @boldsuck, nice to see you here. 👋🏻

Thank your for the information. I will have a look at it and most likely fix it.

The next version (2.8.0) is not planned to be released this year, so it might be the case, that the fix will be available in early January. However, I try to be fairly flexible with my plans, and if time will tell me to release earlier, it still might happen this year, though I wouldn't count on it.

Feel free to open other issues regarding TOR, when found. I barely test it myself and I don't know lots of people who would actually use it, right in this moment. Therefore, it's nice to see you help me out with the testing. 🙂

[theAkito]

Greetings 👋🏻

This issue is fixed. 🎉

Similar to manimaran website-monitor issue 4 But this time it's not because of the http <-> https protocol.

I've successfully tested with duckduckgo (http & https):

I checked the code again and noticed, that no connection through https is attempted:

webmon/app/src/main/kotlin/ooo/akito/webmon/data/repository/WebSiteEntryRepository.kt

Line 155 in ee80adf

onionConnectionIsSuccessful(rawUrl.removeUrlProto())

The protocol (either http or https) is ignored when attempting to connect.

I found this behaviour acceptable, as it should not matter:

Third, you don’t need SSL/TLS in an onion address (ie. https) since it’s a complete encrypted tunnel with perfect forward secrecy.

That said, I tested your Onion addresses with custom ports and they work fine, now. However, I found out that Orbot is pretty unreliable, so if Onion addresses sometimes stop working for seemingly no good reason, you might need to Force Stop the Orbot app and restart it.

[boldsuck]

Many thanks. Because of the unreliability of orbot: I'll test it with a cell phone only at home via wifi. It's enough if I check 2-3 times a day whether the services are running.

Yeah, there are very few https .onion services. For example Facebook, BBC and Protonmail. They have the money for it. ;-)
The certificates for this are ridiculously expensive, and the identity is leaked when you request one.
More info about: HTTPS for your onion service

[theAkito]

I'll test it with a cell phone only at home via wifi.

In my case I had tested this new feature on the Android emulator. It did not work, so I tried to find a bug in my code. A long time later, I had to realise, that the culprit was Orbot. I had to reboot the emulator to make Orbot work normally, again.

The problem is, that in the case I experienced, Orbot seems to "work" and be "connected", but in reality it does not work.