Unable to connect to adj-noun.local addresses, but can connect via IP and onion addresses

[Tahlus]

I am unable to connect to the server via adj-noun.local addresses, but I am able to connect to the server via its local IP address. I am using Firefox on Arch Linux, and I am getting an ‘unable to connect’ error. I’ve trusted my certificate on the remote machines and gone through the common issues and looked through the forums for answers to no avail. A hard refresh of my browser does not work, nor does restarting both the remote machine nor the server itself.

Additionally, I am able to connect over Tor to the server, so it seems something is wrong with either my installation as it’s unsupported hardware, or something on my local network is interfering as my router is using Openwrt.

Also, and this may be separate, but my services seem to be inaccessible. I’ve installed NextCloud and SearXNG so far, and both of the ‘launch UI’ buttons open a new tab to long-alphanumeric-string.local addresses that give the same error as my adj-noun.local address. Is there a setting to use IP addresses as the WebDAV Base LAN URL for connecting to services?

EDIT: Spelling, words, and moved to StartOS Support from DIY

[StuPleb]

.locals work using Multicast DNS, and if your OS doesn’t have something that handles that, you would be able to resolve a LAN IP from a .local

Many linux distros come preconfigures with mDNS since it’s still very popular with printers, but not all will.

It your case, it looks like you’ll have to manually install either systemd-resolved or avahi. It might be best to search online what would be best for Arch and what the two or three steps to install each one are.

Once that’s done, you should have no problems.

[Tahlus]

Enabling systemd-resolved fixed the issue. Thanks!