Openport add-on — remote access on a stable https URL, no port forwarding

Hi everyone,

I’m the author of openport, a tunneling service I’ve been running since 2014. I run Home Assistant at home and wanted to reach it from anywhere without opening ports on my router — so I packaged the openport client as a proper add-on and I’d love your feedback on it.

What it does

  • Your Home Assistant becomes reachable at a stable address like
    https://abcde.u.openport.io — https out of the box, no port forwarding,
    no firewall changes, no dynamic DNS, no certificates to renew. Works
    behind CGNAT.
  • WebSockets are fully supported, so the frontend and the companion apps
    work normally.
  • The address is tied to the add-on’s stored key and session, so it stays
    the same across restarts, reboots, and updates.
  • Builds for aarch64, amd64, armv7 and armhf.

Setup (about five minutes)

  1. Add the repository in Settings → Add-ons → Add-on Store → ⋮ →
    Repositories
    : https://github.com/jandebleser/home-assistant-addons

  2. Install the Openport add-on and paste your key registration token
    from my devices page into its configuration.

  3. Add this to configuration.yaml (the tunnel reaches HA through a local
    proxy) and restart:

    http:
      use_x_forwarded_for: true
      trusted_proxies:
        - 127.0.0.1
    
  4. Start the add-on — the log prints your public address. Set it as the
    External URL and point the companion apps at it.

Security notes

Your login page becomes reachable from the internet, so strong passwords
and ideally MFA. If you want a gate in front of the login page itself,
there’s an ip_link_protection option: visitors must first open a secret
link before anything is served (it can get in the way of the companion
apps, so it’s off by default).

Pricing, upfront

openport has a free plan that’s fine for trying the add-on, but it has a
small bandwidth cap and short session limits. For permanent remote access
you’d want the Home plan: $5/month or $50/year, with a 30-day free trial.
And to be fair: if you want remote access that also funds Home Assistant’s
development, Nabu Casa’s Home Assistant Cloud is the canonical choice —
openport is for people who want an alternative, or who also tunnel other
things (SSH, a printer UI, other self-hosted services) with the same
account.

Repo & docs: GitHub - openportio/home-assistant-addons: Home Assistant add-on for openport.io — reach your Home Assistant from anywhere on a stable https address, no port forwarding. · GitHub

This is the first release — bug reports, feature requests and blunt
feedback are all very welcome.

and the installation here: GitHub - openportio/home-assistant-addons: Home Assistant add-on for openport.io — reach your Home Assistant from anywhere on a stable https address, no port forwarding. · GitHub
refer to add-on term that has been gone for over a year. I’m sure your LLM wrote this for you, but it is wrong. Those tabs do not exist and that install cannot work as written. Also using the old term instead of App at this point in time will confuse new users that have never here of the old term.
My suggestion is update the term, fix in install instructions so they are correct, maybe even use the My install thing and your users will thank you.
Link to App: dashboard – My Home Assistant

Use this: My Link / EZ-Button to help users install your App

You’re right on all counts, thanks. I’ve fixed the README to the current Settings > Apps flow and kept the My button as the main path: docs: use the current Settings → Apps install flow in the README · openportio/home-assistant-addons@d97e1b1 · GitHub. The old term stuck with me because the developer docs still say add-on, but user-facing docs should match the UI.
Sorry about the LLM, I just don’t have the resources right now to do everything myself.