Rustup command failed

General
1

I am using Ubuntu 24.04.3 TLS. I want to mine Nock.

The first step is…

Install rustup by following their instructions at: https://rustup.rs/

… I go to that url. The first step is…

Run the following in your terminal, then follow the onscreen instructions.

curl --proto ‘=https’ --tlsv1.2 -sSf https://sh.rustup.rs | sh

… and when I run that in my terminal, I get this error…

error: command failed: downloader https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init /tmp/tmp.yvPencg7JD/rustup-init x86_64-unknown-linux-gnu

… I do not know what to do next. Suggestions welcome.

2

That error suggests the download itself is failing. Let’s diagnose and fix this systematically:

First, let’s check if it’s a network/connectivity issue:

bash

# Test if you can reach the rustup server
curl -I https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init

If that fails, try:

bash

# Check basic connectivity
ping -c 3 static.rust-lang.org

Common fixes:

  1. Try with verbose output to see what’s actually failing:

bash

   curl -v --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
  1. If it’s a certificate issue, ensure ca-certificates is installed:

bash

   sudo apt update
   sudo apt install ca-certificates
  1. Download rustup-init directly and run it:

bash

   wget https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init
   chmod +x rustup-init
   ./rustup-init

  1. Check if you’re behind a proxy - if you are, you may need to set proxy environment variables.

  2. Try updating curl:

bash

   sudo apt update
   sudo apt install --reinstall curl

What output do you get from the first curl test command? That should tell us more about what’s blocking the download.

3

Thank you for your help. Here is the output I got from the first curl test command…

curl -I https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init
HTTP/2 200
x-amz-id-2: tfHnfyvLq9NGMPjpYlEyXIxqqlxBnx1Jb1GTixFlgpI/M2JJ9mnFMRMz1sxk2D9VoMom/OKKfIf+HdsdyZT8Ce+t6UhljsR8ow5ob7Zb7bg=
x-amz-request-id: 10X2ZRNMKKP7114Q
last-modified: Mon, 05 May 2025 13:00:56 GMT
etag: “214b70d069c580d89b3188190f679e46-3”
x-amz-server-side-encryption: AES256
x-amz-version-id: RxCLD4Py3HaxabZqfNIqTEOexuyUd_az
content-type: binary/octet-stream
server: AmazonS3
accept-ranges: bytes
age: 81136
date: Sun, 19 Oct 2025 10:31:03 GMT
via: 1.1 varnish
x-served-by: cache-pdk-kfty8610080-PDK
x-cache: HIT
x-cache-hits: 0
x-timer: S1760869863.037315,VS0,VE1
content-length: 20889000

4

Since the direct URL works, download and run rustup-init manually:

bash

# Download it directly
wget https://static.rust-lang.org/rustup/dist/x86_64-unknown-linux-gnu/rustup-init

# Make it executable
chmod +x rustup-init

# Run the installer
./rustup-init
5

Thank you for your help. Direct download & chmod & install succeeded.

I went on to the next few steps. Got to the “clone the repo” and had to install git, a step not listed in the instructions. I know most reading this will think well of course, but every “well of course” not included in instructions comes at a cost and a benefit.

Got to the make install-hoonc step and got this error…

rm -rf .data.hoonc
rm -rf ~/.nockapp/hoonc
cargo install --locked --force --path crates/hoonc --bin hoonc
make: cargo: No such file or directory
make: *** [Makefile:49: install-hoonc] Error 127

1 Like
6

cargo is installed but not in your current shell’s PATH yet. Reload the environment.

source "$HOME/.cargo/env"
make install-hoonc

Or just open a new terminal window, navigate back to the repo directory, and run the make command there again. Either way.

I’ll make a note to add git to the instructions.

7

Thanks again. Was able to progress much further down the list before next error. I tried…

bash ./scripts/run_nockchain_miner.sh

… and got…

Starting nockchain miner with 2 mining threads:
I (13:47:56) [no] kernel::boot: Tracy tracing is enabled
Error: “Invalid mining_pubkey: invalid base58 string length, got 147”

… which didn’t show up at a boot emoji on screen, that I recall, but there you go. Suggestions welcome.

1 Like
8

That sounds like you need to check the mining pubkey for spaces or missing parts. You’re almost there, I think—that’s a formatting issue of some kind most likely.

9

I have checked the address I put after “MINING_PKH=” and there are no spaces, no returns. It is exactly the key that is “Extended Public Key (save this for import)” when I exported the keys.

Suggestions welcome and thanks for your help. I also think I’m close!

1 Like
10

Are you comfortable DMing me on X (my Urbit ship is down today still)? I think we can sort this out with a screenshare.

11

Sure thing. My x is mogtus_sanlux , send message and I’ll see you there. And thanks again.

1 Like
12

Follow-up for posterity: Was using zpub key instead of address, which I didn’t even notice at first so it’s a bit subtle.

I propose adding this as an error type: Add ZPubUsed error variant for base58 decoding by sigilante · Pull Request #66 · zorp-corp/nockchain · GitHub

1 Like
13

Thanks to sigilante, problem identified and corrected and mining begun.

1 Like
14

It’s still prior the v1 switchover but I found on a earlier run this afternoon that it would take a v0 key to run miner but not a v1. This is after pulling and rebuilding the sigilante pr from this morning.