I encountered the same error on my end and when I finally deleted my helm configuration folder (~/.config/helm), access worked fine. There were various entries in the config.json of the registry directory whose paths were only marginally different, but which apparently caused this error.