Reactor Build 26284 stuck at Loading Reactor UI

[tamorgen]

Good morning all,
I'm having an issue with the latest version of MSR. I'm unable to get past "Loading Reactor UI..."

I run a MSR image in Portainer on Proxmox as a Docker VM. This has served me well for about the past 18 months. Previously I ran MSR as a bare metal install.

To secure and access my local images, I run a Cloudflared LXC and run a Cloudflare tunnel. The Cloudflare tunnel for MSR points to my Proxmox server's local IP port 8554. I've used username/password since it became an option for MSR.

I've read the notes about new Access control and reverse proxies. I'm not sure that this new feature is what is causing my issue, but this is the only thing I can think of at the moment.

I also want to point out that if I access the site locally via IP, the site does load properly, albeit with a Not Secure warning:

Thanks in advance for any advice.

Running:
Reactor (Multi-hub) latest-26284-5f780cf0
ZWaveJSController [0.1.26048]

[tamorgen]

Okay, I determined the issue. I looked in the logs, and MSR is actually seeing the IP of the source host and denying the entry. I've added the assigned IP of from my ISP, as well as my work network to the allowed IP list. I can now access MSR from my workstation at work, as well as my iPhone with VPN to my home network turned on, and my local network as before. What I don't know about, is if my ISP reassigns my IP address, what I can do about it, as this could cause me to have to manually add that IP address every time it's changed. Historically, they haven't changed it often, but I may have to figure a way out to automatically update the config.

[tamorgen]

@toggledbits
This may be a feature request, which would solve the dynamic IP issue in mentioned in my previous post. Would it be possible to use domain names in the allowed list instead of just IPs (I tried, doesn't appear to work)?

As I mentioned in the original post, I access MSR via the my Cloudflare domain name. Previous to this update, I was able to access it from anywhere. This lock down is probably a good thing, but it now creates a potential issue when I try and access MSR from my local network.

Cloudflare automatically updates the Origin IP of my network, which is the same as the IP my ISP assigns me. If I put my domain name in as an allowed source, then anytime my ISP reassigns me an IP address, then that source IP would be allowed.

My other option may be some sort of bash/cron script, but I'm not sure how successful it would be.

[toggledbits]

Have you set any of the new proxy configs?

[toggledbits]

I found two cases where proxy-handling behavior can be triggered even though Reactor isn't configured with proxy info. Build 26287 contains fixes for those.

[tamorgen]

@toggledbits said in Reactor Build 26284 stuck at Loading Reactor UI:

Have you set any of the new proxy configs?

I'm not seeing about proxy configs in the reactor.yaml file. I had not set anything previously.

I'm looking the docs and I'm not seeing where the proxy needs to be set up.

Reactor - Multi-Hub Automation

I guess the reactor.yaml file doesn't automagically get updated when a new docker image gets released.

[tamorgen]

@toggledbits said in Reactor Build 26284 stuck at Loading Reactor UI:

I found two cases where proxy-handling behavior can be triggered even though Reactor isn't configured with proxy info. Build 26287 contains fixes for those.

I updated to the 26287 build, commented out my public IP, and the behavior returned.

I put removed the comment so it's working currently. As a work around, I set up a crontab that checks my public IP hourly, replaces the line with the IP (new or not), then reboots the docker instance. This is working but, I have a feeling the hourly restarts will bite me at some point.

[tamorgen]

I found the proxy section in the doc (search function works great).

I added my cloudflare URL in a below baseurl and recommented by public IP.

proxy_baselurl: https://reactor.xyz.com #not xyz.com

I am now getting Access Denied.

Edit: I also tried it with quotes around the URL. I'm not sure why, but in your documentation you have quotes around the baseurl URL and the proxy_baseurl with an IP, but in the next section with a FQDN, there is no quotes. Is that intentional, or does it matter?

[toggledbits]

@tamorgen said in Reactor Build 26284 stuck at Loading Reactor UI:

proxy_baselurl: https://reactor.xyz.com #not xyz.com

Must include port number

@tamorgen said in Reactor Build 26284 stuck at Loading Reactor UI:

Edit: I also tried it with quotes around the URL. I'm not sure why, but in your documentation you have quotes around the baseurl URL and the proxy_baseurl with an IP, but in the next section with a FQDN, there is no quotes. Is that intentional, or does it matter?

Best practice to quote it. Makes no difference to Reactor as long as the YAML parser accepts it (the quotes assure that).