If a community isn't known to the instance, Connect shows a blank page with "could not find a community with that name". I'm on a small instance, so clicking new communities tends to lead to this error rather than showing the community. (tbf the web interface for Lemmy pretty much does the same thing) If I first search for the full URL on the web interface, Connect will then find it. Is it possible for Connect to work around this issue, by maybe doing a search for the full URL and retrying before showing this error?