Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved
Collapse
Discussion Forum to share and further the development of home control and automation, independent of platforms.

Global Moderators

Forum wide moderators

Private

Posts


  • UI not loading after upgrading to 26318
    toggledbitsT toggledbits

    @tunnus said in UI not loading after upgrading to 26318:

    This also means that I cannot use "http://reactor_host:port/diag/clear_authtrack?askauth" command to clear the block (or use any other source IP for login). Docker container stays up & running and does not exit.

    By the way, I didn't fully catch this on my earlier reading, but this is not true. At least, it's not the design. Blocking only blocks a single host IP address. You should be able to make the request to the clear_authtrack endpoint from any other IP (as long as you can correctly authenticate from that IP). You definitely won't be able to do it from the same IP that got blocked, of course, but any other IP should work.

    The other thing is that that endpoint will not stop the docker container. That would actually be an unexpected result (bug) for that endpoint.

    Multi-System Reactor

  • UI not loading after upgrading to 26318
    toggledbitsT toggledbits

    Stop Reactor, remove the auth.json and auth.dval files from the storage directory, restart Reactor.

    This will also invalidate all auths for all clients. Everyone will need to log in again.

    If you want something a little less dramatic, stop Reactor, edit auth.json and remove the contents of the value under authtrack (i.e. make it read value: {} with nothing between the curly braces). Then delete auth.dval and restart Reactor.

    Multi-System Reactor

  • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
    toggledbitsT toggledbits

    Forgot to mention, this version also supports HTTPS for the hub. Your hub username and password travel in cleartext if you don't use HTTPS in both your browser and Reactor, so it's worth considering turning it on in the hub and changing your source to https://... in your HubitatController configuration. If you use a self-signed certificate or use the hub's default certificate (i.e. you don't provide a signed certificate of your own), you must add ignore_certificates: true as well.

    Multi-System Reactor

  • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
    toggledbitsT toggledbits

    OK. Build 26318 supports the updated firmware (2.5.3).

    Multi-System Reactor

  • Reactor (Multi-System/Multi-Hub) Announcements
    toggledbitsT toggledbits

    Reactor build 26318

    • HubitatController: Fix hub login failure in hub firmware 2.5.3 and above.
    • Security: New Access Control configuration elements bypass_blocking and bypass_mfa. The former prevents IP addresses with multiple authentication failures from being blocked; the latter allows login without MFA when require_mfa: true is configured. Both expect an array of CIDR host or subnet addresses. See docs
    • DynamicGroupController: Prevent a group from having itself as a member.
    • HassController: Bless HA to 2026.11.1
    Multi-System Reactor announcements

  • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
    toggledbitsT toggledbits

    @3rdStng said in Hubitat upgrade 2.5.3.123 may have broken login:

    This error may be due to the container stopping?

    Correct assessment for the Engine not running messages.

    @3rdStng said in Hubitat upgrade 2.5.3.123 may have broken login:

    Disabling Hub Login Security, and commenting out my username and password in the config.yaml, allowed for the status updates to be sent/received by MSR. So this is a work around, but I would prefer to have a login enabled.

    That would be a correct workaround for the moment. When I get time this afternoon, I'll see what changed at the hub firmware and what I can do about it.

    Multi-System Reactor

  • [Resolved] Hubitat upgrade 2.5.3.123 may have broken login
    toggledbitsT toggledbits

    When hub login is enabled at the hub, events are not sent over the Websocket channel until HubitatController gets a successful login. I quickly reviewed the release notes for 2.5.3.123, and nothing jumped out at me, but I'm running to an event right now, and I'll be tied up in the morning tomorrow, so I won't get a chance to dig into this until tomorrow afternoon at the earliest.

    Do you know what version of firmware you were running prior to upgrade? It may be in messages in previous reactor.log files.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    I'll take some responsibility here for not asking to see the entire file and just relying on snippets (hard to tell indent and relation to other data).

    BTW, the give-away was this:

    [latest-26298]2026-11-03T16:50:01.685Z <httpapi:null> httpapi#1 ACL no match: user tmorgenthaler to group:api_allowed
    

    It's saying that the user isn't in the group. But the group was in your config file... so this says it can't see your group... and the indenting explained why.

    Multi-System Reactor

  • Reverse proxy & API ACL
    toggledbitsT toggledbits

    The X-Forwarded-For header is only handled for the trusted_proxy list IPs.

    Multi-System Reactor

  • MFA
    toggledbitsT toggledbits

    The indenting of your groups section is very goofed up. api_allowed and everything below it should be outdented two spaces... same alignment as admin, not underneath it as you've shown. Also the two lines showing after applications under admin... no idea where that comes from or what it's supposed to do. Not sure what the intent was, but that's not anything Reactor will see or care about.

    proxy_baseurl and pass_all_proxy do not go in users.yaml.

    Multi-System Reactor

Member List

CatmanV2C CatmanV2
therealdbT therealdb
toggledbitsT toggledbits
akbooerA akbooer
DesTD DesT
rafale77R rafale77
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Unsolved