Cannot connect to umbrel.local on Chrome and Brave

Support and Troubleshooting
1

Hi There,

I cannot connect to umbrel.local even using the right internal IP address via Chrome or Brave. I can just through Firefox through a private tab (for both umbrel.local or with the IP)

Can you please advise how to connect via Chrome or Brave?

Thanks,

2

Hey friend @FSM this is usually because of a Chromium issue with how it and the local machine remembers things… Safari resolves it right away but for this i think this will resolve your problem going forward to reduce frustration and is what I currently did for my Chrome so far,

(Usually if you like clear DNS, restart, this doesn’t occur and works out of the box),

Let us know if you get any specific errors further, or what your setup is like, when loading the page or anything:

(When entering in your Umbrel IP it should work fine and be reachable), and Safari works fine for umbrel.local

Step to take:

On your local machine, your computer not Umbrel, use terminal/command prompt/power shell and run the IP of your Umbrel to map the IP to Umbrel to resolve it, should work for Brave and Chrome let us know, and immediately fixes it going forward, command to use so it remembers:

echo "192.168.1.x umbrel.local" | sudo tee -a /etc/hosts

(given you used arp -a command or ssh’d into umbrel to find its correct IP, or in your router’s connected devices info it should be getting detected and reachable, and replace 192.168.1.x with your Umbrel’s IP for the command above)
see Umbrel FAQ for more info on SSH etc. if needed.

That should work above for the command just running once ^^ and you shouldn’t have to worry about these known host troubleshooting steps…

Some more details from a little research not all of this is really applicable as the host machine is handling a lot of this it seems but for anyone interested, some of it might be redundant after this just more background things: `.local` domain for each app using mDNS · Issue #1985 · getumbrel/umbrel · GitHub

Use the IP address of your Umbrel directly in your browser so it remembers (what we did above) (e.g. http://192.168.1.x) to ensure these weird Chrome rules set like “CORS” etc. are remembered (and for your troubleshooting, let us know if any other error)

Another step to take

  • Clear Chrome’s DNS and socket caches via navigating to chrome://net-internals/#dns and can click clear host cache

to avoid like losing all your cookies for logged in sites or doing the other known hosts thing if you’re an IT manager and store a bunch of PuTTY keys like in your hosts files