Opened 4 years ago

Last modified 4 years ago

#20721 new defect

Orbot and Owntracks

Reported by: dbenhart Owned by: n8fr8
Priority: Low Milestone:
Component: Applications/Orbot Version: Tor:
Severity: Normal Keywords: Owntracks, MQTT
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


I am using the newest versions of the Owntracks and Orbot apps to send data to a private MQTT broker. The broker is exposed as a TOR Hidden Service and ties into my Home Assistant setup. I know that Owntracks works, at least some of the time, because if I'm at home and change the host IP from the .onion address to the server's IP address, it connects and updates correctly. I know that Orbot works because I also have the web front end for Home Assistant exposed as a Hidden Service and I can connect to that via Orfox. The problem is that when I change the MQTT Broker host to the .onion address, Owntracks enters a state where it is always connecting, but never connects. I have Orbot set to run Owntracks through its "app-VPN", which I've been told will allow it to resolve a .onion address. I'm not sure which component is causing a problem, so I'm checking with all parties.

Child Tickets

Change History (2)

comment:1 Changed 4 years ago by n8fr8

This is with the latest version of Orbot from Google Play?

comment:2 Changed 4 years ago by dbenhart

Yes, at least the Play store doesn't show any updates. I'm using Orbot version 15.2.0-RC-8-multi.

Note: See TracTickets for help on using tickets.