Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #20721
Closed
Open
Issue created Nov 18, 2016 by Trac@tracbot

Orbot and Owntracks

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.

Trac:
Username: dbenhart

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking