Cockpit doesn't install correctly for 32-bit or 64-bit raspberry pi os, pi 4gb?

[VersatileNinja]

I was able to get into retronas, but I noticed when I try to install cockpit, it will go through but at the very end it shows this very long red error message.

When I check services running, cockpit is not running. When I try to access the pi through the web browser ipaddress:9090, it doesn't work, because cockpit isn't working.

BUT if I install it manually via: `sudo apt install cockpit', then it works! Why is that?

[sairuk]

Can you add the error to this issue to aid in troubleshooting?

[VersatileNinja]

I will record the error and post it tomorrow (maybe I can get a screenshot to share too), thanks in advance.

[sairuk]

Hi please also review this issue #8 to see if is related at all

[VersatileNinja]

I did a fresh install on my pi 4gb, 32-bit raspberry pi os. Afterwards, I enabled ssh using raspi-config, did not use a blank ssh file for example.

Now I go to install cockpit from the retronas interface, and I get the red error (see image provided).

I know that if I were to install cockpit manually outside of retronas, it will work, but I'd like to help you troubleshoot how to make installer work? I'm a raspberry pi novice, but glad to help where I can.

[sairuk]

This looks like you are having the same apt-key problem as mentioned in issue #41

[VersatileNinja]

Thanks for the tip. That did the trick and I fixed it by the following (for anyone in future curious what I did):

I did the following:
sudo nano /etc/dhcpcd.conf

Then added at the bottom for CloudFlare public DNS:
static domain_name_servers=1.1.1.1 1.0.0.1

Restart the service:
sudo service dhcpcd restart

Afterwards, went back into retronas and cockpit installed successfully! Not sure why it would install correctly outside of retronas even though I didn't change the DNS, but at least it works the way it is supposed to right now.

[retinoic]

Thank you @VersatileNinja for the solution. Had the same issue with fresh 64 bit RPi OS Lite install.

[danmons]

This looks like you are having the same apt-key problem as mentioned in issue #41

I'll try and get a fix out for this soon. I'm not sure why certain setups aren't able to resolve the key servers. "works for me" on my stock RPiOS bullseye 64bit.

Fix will be to avoid the key servers and just grab the Debian signing keys via a dpkg file.

[sairuk]

I will reopen this while we are pending a fix so we have visibility on occurrence of this iss

[danmons]

Sorted this just now. New method no longer uses "apt-key" nor points to keyservers listening on weird ports.

Instead it grabs the .deb package containing the keys (with a couple of known working mirrors as fallback to each other) and installs that. It's more compliant with the new APT key storing method, and should be more reliable for people either with poor DNS servers or restrictive firewalls.