Hello, I just got a Linux laptop and I’m trying to connect to my server, but the .local addresses aren’t working. I can get there via the IP and tor. I’m running Kubuntu 24.10.
Troubleshooting steps:
. it works on my old win10 laptop
. VPN is off
. followed the docs install guide
. root CA check works when connecting via IP
. cleared the cache
. checked that avahi-daemon is running
Is there something obvious I’m missing?
What browser are you using to access your server’s UI?
We usually recommend Firefox. Also make sure to install your browser direct from the source and not flatpak or other containerized browser version.
Using brave browser! And installed it from their website.
Álvaro asked about the browser because you very specifically said avahi-daemon is running. If you’re sure, that should be all you need.
Now, I assume when you say “.local addresses aren’t working”, you’re only talking about your individual services, right?? That your main adjective-noun.local is working fine?
If, please clarify what is working and what is not.
No the main adjective-noun.local isn’t connecting either. Connects on my windows laptop though.
Can you show us the output of this command:
sudo systemctl status avahi-daemon
Do you see any .local addresses on the network when you do:
avahi-browse -part
How are you connected to the network that your server is on, with respect to your linux computer?
If by wireless, are you on a guest network? (don’t be… guest networks block access to the LAN)
If by ethernet, is there a router or other network device between the linux laptop and the server?
Console output:
$ sudo systemctl status avahi-daemon
● avahi-daemon.service - Avahi mDNS/DNS-SD Stack
Loaded: loaded (/usr/lib/systemd/system/avahi-daemon.service; enabled; preset: enabled)
Active: active (running) since Fri 2025-01-17 09:43:51 CST; 1 week 4 days ago
Invocation: b6bed8af94964a48aec6e6c20e5a4d07
TriggeredBy: ● avahi-daemon.socket
Main PID: 947 (avahi-daemon)
Status: "avahi-daemon 0.8 starting up."
Tasks: 2 (limit: 37376)
Memory: 1.5M (peak: 2M)
CPU: 3.011s
CGroup: /system.slice/avahi-daemon.service
├─947 "avahi-daemon: running [calvin-precision7560-3.local]"
└─988 "avahi-daemon: chroot helper"
Jan 28 17:44:26 calvin-precision7560 avahi-daemon[947]: Interface wlp147s0.IPv4 no longer relevant for mDNS.
Jan 28 17:44:26 calvin-precision7560 avahi-daemon[947]: Withdrawing address record for fe80::4f69:9876:68d9:e250 on wlp147s0.
Jan 28 17:44:26 calvin-precision7560 avahi-daemon[947]: Leaving mDNS multicast group on interface wlp147s0.IPv6 with address fe80::4f69:9876:68d9:e2>
Jan 28 17:44:26 calvin-precision7560 avahi-daemon[947]: Interface wlp147s0.IPv6 no longer relevant for mDNS.
Jan 28 17:44:27 calvin-precision7560 avahi-daemon[947]: Joining mDNS multicast group on interface wlp147s0.IPv6 with address fe80::fdf2:dae3:c270:50>
Jan 28 17:44:27 calvin-precision7560 avahi-daemon[947]: New relevant interface wlp147s0.IPv6 for mDNS.
Jan 28 17:44:27 calvin-precision7560 avahi-daemon[947]: Registering new address record for fe80::fdf2:dae3:c270:5072 on wlp147s0.*.
Jan 28 17:44:27 calvin-precision7560 avahi-daemon[947]: Joining mDNS multicast group on interface wlp147s0.IPv4 with address 192.168.11.72.
Jan 28 17:44:27 calvin-precision7560 avahi-daemon[947]: New relevant interface wlp147s0.IPv4 for mDNS.
Jan 28 17:44:27 calvin-precision7560 avahi-daemon[947]: Registering new address record for 192.168.11.72 on wlp147s0.IPv4.
Second output:
$ avahi-browse -part
+;wlp147s0;IPv6;batty-eel-2\.local;Web Site;local
+;wlp147s0;IPv4;batty-eel-2\.local;Web Site;local
=;wlp147s0;IPv6;batty-eel-2\.local;Web Site;local;batty-eel-2.local;2600:1700:1970:3230::2d;443;
=;wlp147s0;IPv4;batty-eel-2\.local;Web Site;local;batty-eel-2.local;192.168.1.194;443;
I tried to connect to batty-eel-2.local, still a 404.
My server is connected to the AT&T router via ethernet, and my laptop connects via Wi-Fi.
It can’t be showing a 404. That would be mad. Perhaps a failure to find the host, like a “unknown host” or similar?
It seems the next best step would be to follow our guides and set up Firefox, installed from the command line. Get that to work to confirm everything is fine, then figure out Brave.
Yeah sorry that’s what I’m getting. Brave says:
This batty-eel.local page can’t be found
No webpage was found for the web address: http://batty-eel.local/
HTTP ERROR 404
I installed firefox from cli, set it up following the guide, still getting the same error:
Hmm. We’re having trouble finding that site.
We can’t connect to the server at batty-eel.local.
If you entered the right address, you can:
Try again later
Check your network connection
Check that Firefox has permission to access the web (you might be connected but behind a firewall)
So I have no idea what the issue is.
That is a bit odd. A true 404 error is generated by the server, meaning that the server was found, but the resource requested doesn’t exist on the server. In your case it’s telling you the server can’t be fund, but the server said that page you requested isn’t available.
It’s like if I sent to to someone’s house to see if they were home, and you came back to me, and said “nope. No on is home.” Then I asked “how do you know?” You said “Because I was never able to find the house, but when I got there, the person that was there said no one was home.”
This discombobulation sounds like a network error to me. You may want you power cycle your router. If you have anything other than a flat network setup, we’ll need some info about it.
This is the much more rational error message I get in Chromium in Windows.
If I get some time here, I might do an install of Kubuntu to take a look. Something is off.
That is curious indeed!
I have verified that .local resolution works in Firefox, on Kubuntu 24.04, out of the box. I have not yet tested Brave, and likely won’t get to it for at least a few days.
So for now, I still suspect a network issue on your end. Perhaps a mesh setup, a guest wifi, and/or vlan or firewall settings interfering? Let us know what you find. I’ll let you know when I get a chance to test Brave.
