Closed tfc closed 5 years ago
I did run into the same problem.
You can check with
nix path-info --store http://<hostname>:<port> --json <some-path> | grep sig
that nix-serve
doesn't serve signatures.
I spent a few hours on this problem, trying to figure out why nix was unhappy with nix-serve's signatures, until @cleverca22 in #nixos (thank you) pointed me to /root/.cache/nix
- removing that on the client machine fixed the problem for me. I suspect it had cached .narinfo's with missing signatures, because I previously started nix-serve without NIX_SECRET_KEY_FILE=
.
Closing this ticket, as i cannot reproduce it on other machines any longer (the installation on which i had the problem does not exist any more). I guess it was the ~/.cache/nix
thing.
I was able to reproduce this. Deleting ~/.cache/nix
fixed it for me.
Just hit this issue as well, could be have:
~/.cache/nix
or /root/.cache/nix
)This still happens. Are we sure we want to keep this issue closed? Is there no better solution than to let the user figure out it's ~/.cache/nix
?
Hi there,
so i have 2 single user installations of nix on an ubuntu machine and a centOS machine. I installed nix using the default installer last week thursday.
Then i set up the ubuntu machine as binary cache following this guide written by Gabriel.
The
nix-serve
process just runs calmly, but the client does not accept the signatures:(need to run with sudo to serve on port 80 because of intranet firewall restrictions)
the nix config looks like this:
As far as i understand,
nix-serve
should sign everything it serves on the fly. But this does not seem to happen or it happens with the wrong signature, right? I double- and triple-checked if the target has the right pub key set and also generated new keys for the whole procedure, but to no avail.