No access to Alby Hub UI over local address

I updated Alby Hub from 1.19.0 to 1.20.0 from the update menu. All went well. Only when I launch the Alby Hub UI, it shows the message:

Hmm. We’re having trouble finding that site.
We can’t connect to the server at xxxxxxxxxxxxxxx.local.

The Alby Hub status shows:

Running
Web UI Success : Alby Hub is ready
Dependencies LND satisfied

I do have access to Alby Hub over the Tor address, over the browser extension and via the Alby Go app on my phone.

I already restarted the Alby Hub service and rebooted the devices, but this did not fix the problem. What else can I do to tackle this issue?

What makes you think this is related to Alby Hub? Are all your other services’ .local interfaces working and it’s just this one that isn’t?

Assuming that you can access the interfaces of the other services, we might need to look at the Alby Hub logs.

However, if you have confused an issue with your client OS where it can’t access ANY of your .local address for individual services, then you’re probably using Windows and will need to follow this guide: Start9 | Connecting Locally

That’s a good question, I hadn’t thought of that. Because Alby Hub is the most used service, I forgot to check the others. Indeed, they are also not reachable via the .local address. Thanks for the link.

A Bonjour repair quickly solved this issue.
Thanks for your help @StuPleb

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.