warning: error: unable to download 'https://channels.nixos.org/nixos-25.05': SSL peer certificate or SSH remote key was not OK (60) SSL certificate problem: unable to get local issuer certificate; retrying in 261 ms
warning: error: unable to download 'https://channels.nixos.org/nixos-25.05': SSL peer certificate or SSH remote key was not OK (60) SSL certificate problem: unable to get local issuer certificate; retrying in 516 ms
warning: error: unable to download 'https://channels.nixos.org/nixos-25.05': SSL peer certificate or SSH remote key was not OK (60) SSL certificate problem: unable to get local issuer certificate; retrying in 1121 ms
warning: error: unable to download 'https://channels.nixos.org/nixos-25.05': SSL peer certificate or SSH remote key was not OK (60) SSL certificate problem: unable to get local issuer certificate; retrying in 2421 ms
warning: error: unable to download 'https://channels.nixos.org/nixos-25.05': SSL peer certificate or SSH remote key was not OK (60) SSL certificate problem: unable to get local issuer certificate; using cached version
unpacking 1 channels...
Firefox also gives me a warning when I try to go to channels.nixos.org and curl says the same thing.
I thought it might just be a simple wait and see issue but its been going on for at least two weeks now and I really have no idea what is going on. I can visit other https sites just fine so I’m stuck.
Just another user. I don’t see that behavior on my NixOS machine or other devices. Sounds like a certificate problem that is most likely to be local to your machine. Have you tried accessing channels.nixos.org on a different device you own (like a phone if nothing else), and see if you are getting the same issue?
If you try to boot into an older generation, do you see the same errors with nixos-rebuild?
I tried on other devices and I believe I found the issue, thanks.
My home wifi network provider blocks the site. When I try to go to channels.nixos.org on my mobile devices I get a warning from the network provider but if I use my phone’s internet (which is from a different network) it works fine.
Hence the wrong fingerprint from the openssl that’s done its job and is waiting for more input and might therefore seem “stuck”
Most likely this is a MITM attack (from your provider for semi-legitimate reasons) abusing DNS being unencrypted. You can try using e.g. https://quad9.net/ 's DoH (https://dns.quad9.net/dns-query) as your DNS server instead of what your wifi gives you via DHCP.