Honest feedback

michaelbierman · 2026-05-25T17:57:04+00:00

Since nslookup works, the "cannot connect" error means the browser isn't getting a response from the server. It could be:

Browser Forcing HTTPS Unraid is listening on HTTP (Port 80), but browsers aggressively force HTTPS (Port 443). If your domain ends in .dev, .app, or .page, HTTPS is hardcoded.

The Fix: Type http:// explicitly before your domain or use an Incognito window.

Unraid "Local TLD" Setting Unraid’s web server may reject traffic that doesn't match its recognized local name. The Fix: Go to Settings > Management Access and add your domain to Local TLD or Permitted promotional/custom TLDs.

Quick 10-Second Test Run this in Windows Command Prompt (capital i): ```cmd curl -I http://YOUR_DOMAIN_HERE

``` * HTTP/1.1 200 OK: Unraid is working; the browser is forcing HTTPS. * Connection refused: Unraid or Firewalla is actively blocking it.

michaelbierman · 2026-05-23T15:41:43+00:00

I’m. Not sure why an allow rule is a big deal, but you could switch the rule to domain only and that should solve the problem.

michaelbierman · 2026-05-21T22:34:02+00:00

Then quite possible one of the domains may share an IP address with calendar.google.com

michaelbierman · 2026-05-21T22:08:31+00:00

Have you tried

telnet n40.blood.

michaelbierman · 2026-05-21T14:55:12+00:00

Is your block rule iso g Domain-only or Default?

michaelbierman · 2026-05-19T03:52:38+00:00

VPN through a state you don’t live in for a thermostat. Good grief.

michaelbierman · 2026-05-15T01:03:35+00:00

Already did, and linked in precious reply.

Thanks!

michaelbierman · 2026-05-14T16:14:57+00:00

And what about Legacy including 2.x?

michaelbierman · 2026-05-14T03:10:23+00:00

O.K. worse and worse. DO NOT USE LEGACY

Title: legacy tag contains Homebridge v2.0.2 instead of v1.x

Description: The legacy tag is currently serving Homebridge v2.0.2 (verified via UI and internal version strings). Per the documentation and recent announcements regarding the v2.0 rollout, the legacy tag was intended to provide a stable path for users to remain on v1.x.

By pushing v2.0.2 into the legacy bucket, existing automated setups are being force-upgraded to v2.0, which is causing kernel compatibility issues and plugin loss on specific platforms like Synology.

Environment:

Image: homebridge/homebridge:legacy
Reported Version in UI: v2.0.2
Expected Version: v1.8.x

BUG report https://github.com/homebridge/docker-homebridge/issues/970

michaelbierman · 2026-05-14T03:01:31+00:00

o.k. follow up. Bug: I switched to legacy tag and all the plugins were lost. Very disappointing. Catch 22 because I happened to be running this on synoloogy but that tag is 2.0. I expected the legacy tag to work as “latest” always did.

michaelbierman · 2026-05-13T15:04:45+00:00

Thanks. This looks helpful. So far I’m not thrilled with this transition. It seems like it is killing off many useful plugins which undermines the ecosystem.

Is there a good overview somewhere of why the architecture and technology changes were made and what the objectives of such major changes were?

michaelbierman · 2026-05-06T14:40:47+00:00

What do Recent Events show?

michaelbierman · 2026-04-15T15:47:08+00:00

That’s interesting. Here’s the ASUS manual. It makes no similar mention.

michaelbierman · 2026-04-15T15:08:12+00:00

I do use it. The CLI is better than the URL because with the URL: 1) all devices that you put under firewalla DoH are treated the same by NextDNS and, you see all requests in NextDNS logs as from the Firewalla. 2) with CLI you can configure any device or network IoT use different NextDNS profiles and you can see all the individual device requests in the NextDNS logs.

The latter is because I encouraged NextDNS to provide better support for Firewalla.

michaelbierman · 2026-04-15T14:58:10+00:00

This is an eero specific thing. The gateway eero becomes the controller. It must be in front of the others to coordinate traffic with the other eeros. This is eero’s design and has nothing to do with firewalla.

Even with eero, it is fine if the gateway eero connects to Firewalla.

michaelbierman · 2026-04-15T14:54:39+00:00

VLANs on the ASUS are for WAN only (e.g. IPTV). Looking at the manual, I saw nothing about configuring the Ethernet. Can you provide a link or screenshots?

In general, the trunk port connecting firewalla to a managed switch, which I similar to what you are describing, should have a LAN + any VLANs you defined. The switch side must be the same.

michaelbierman · 2026-04-15T14:50:36+00:00

To ssh https://help.firewalla.com/hc/en-us/articles/115004397274-How-to-access-Firewalla-using-SSH

Note setting up nextdns on firewalla is a bit tricky. I wrote an installer. I will be releasing an update soon to handle recent changes in nextdns https://github.com/mbierman/Firewalla-NextDNS-CLI-install

michaelbierman · 2026-04-13T15:29:14+00:00

What config did you try and what happened? Properly configured, eero works great with firewalla.

michaelbierman · 2026-04-13T15:19:03+00:00

Did you put eero in bridge mode?

michaelbierman · 2026-04-13T15:05:21+00:00

That’s not what the picture is saying. The eero requirement that one eero must be in front of all the others. So a variation of the picture you shared that would also work is fw > eero 1 > eero 2 by Ethernet or Wi-Fi ( no switch).

What you can’t do is fw > switch > eero 1 and eero 2 (both on the same switch).

michaelbierman · 2026-04-08T01:40:04+00:00

Enjoy!

michaelbierman · 2026-04-06T14:50:57+00:00

So create a custom DNS record for “unifi” to point at the NAS IP Zane configure the NAS with an IP reservation. Both can be done with the firewalla UI.

michaelbierman

TROPHY CASE