FAQ:Reason for a Not Found Error (404) on a Repository
From rPath Wiki
| FAQ | ||
| Question: Why does Conary give me a 404 message for a repository I know to be working? | ||
Answer: Conary does not work behind certain transparent caching proxies. However, due to the fact that it is functionally impossible to cache SSL transactions, it is possible to tell Conary to use SSL and work around this issue.
To do so, edit your /etc/conaryrc with a repository map for each repository you need access to. For example:
repositoryMap conary.rpath.com https://conary.rpath.com/conary/