After configuring panamax and cargo, the later keeps attempting to connect to panamax.internal
ivan-jli opened this issue · 3 comments
ivan-jli commented
Am I doing something incorrectly? I greped for ‘panamax.internal’ under ~/.cargo and panamax/mirror, no results. Why cargo still searches for this name?
ivan-jli commented
$ cargo build
warning: spurious network error (1 tries remaining): (6] Couldn't resolve host name (Could not resolve host: panamax.internal)
wcampbell0x2a commented
What is your base_url set to in the mirror.toml file?
k3d3 commented
Make sure your base_url in mirror.toml is set to something other than panamax.internal, and then run panamax rewrite . to update the index with the new base_url.
The reason it cargo tries to connect to panamax.internal is because that's what's set in crates.io-index/config.json. The above steps should fix it.