I have faced this in one of our test lab that time I just used the workaround which you can also try by downloading this catalog file directly on Root Server & then creating prefetch & implementing in a custom fixlet of catalog download.
And as per url which you have mentioned it seems its downloading from local server that could be your LMT server, as per my understanding 127.0.0.1 should be the server IP address thats reason why its getting failed to download.
Have you tried browsing this url directly from the server where you have installed LMT, also download latest catalog fixlet & run from LMT site --> Management -->Catalog update.
How would I download it directly to the root server?
I am running this fixlet called “Catalog Download (Version:XXXXXX) from my BESConsole root server not the LMT server…if I take this URL I get the " this page does not exist”
Same as if Im log directly on my LMT server (RHEL). I go to the URL and page does not exist. So I cant import it to the location LMT>Mgmt>Catalog update
I am trying to understand, how did you get that fixlet into your console.
There is a trigger that creates such action when catalog is imported and there is manual running of the fixlet downloaded from web UI.