Hello 
I am using a Mac Pro M1 with Sonoma 14.6.1 and I have been using Boundary Desktop v2.3.1 to connect to targets for months, since at some point it stopped working as the targets list was stuck showing a “Updating cache…” next to the “Refresh” button.
At that point I was seeing an old target (which shouldn’t be there) instead of a new one I had access to (which wasn’t showing in the list); I did try logging out and in at least 12 times before giving up on that, until my last attempt was to completely uninstall Boundary, remove its ~/.boundary folder and re-install it again.
Using brew, I re-installed Boundary Desktop v2.3.1 and I’ve opened it, then I’ve set the company’s cluster URL and it failed to connect, but the weird thing here is that it also completely dropped my laptop’s internet connection which is very strange. The latter went back up after closing Boundary Desktop again but still the issue persisted.
Now, the cluster URL I’m using is reachable without any proxies or VPNs, so for now let’s assume its address to be https://www.example.com;
If I do nc -vz www.example.com 443 from the terminal I get a successful response so it seems like Boundary is messing up with some DNS configuration or anything related to it, but I truly have no idea how to make it work again.
1 Like
Hi, is it possible you installed Boundary via the Boundary installer? This will include the Boundary Client Agent, which is a local DNS daemon that only works with enterprise deployments. It shouldn’t cause any problems for non-enterprise deployments, but if you are seeing networking issues that might be a place to start investigating. The docs have a troubleshooting section, but if you’re not using Boundary Enterprise (or HCP Boundary), you may want to uninstall Boundary again and reinstall it using the Desktop Client download from here: Install | Boundary | HashiCorp Developer.
Hello @jbrandhorst ,
Thank you for your quick reply!
I’ve installed Boundary again using the Boundary installer and yes, connecting to the cluster URL worked, so I am assuming not having the DNS daemon was messing up my internet connection completely.
However, I am now facing the original issue with the targets list showing a “updating cache…” message next to the “refresh” button. I know that I am assigned to a target but I don’t see anything on the desktop app, any ideas?
Hm, you could try restarting the client cache with boundary cache stop && boundary cache start -background. Not sure what else is going on here. Can you try using the CLI to browse the targets?
Hello @jbrandhorst ,
Sorry for my late reply but I wasn’t available for the last week 
I’ve tried with the CLI and it didn’t work out either, however, we’ve found an issue on our side when assigning targets and logging in to Boundary. The login token had no access to cache (hence the cache error) and targets were not assigned correctly, once that has been solved everything went back to normal.
Thanks a lot for your help!