Issue with NO_PUBKEY

1. offizieller Beitrag

    I've recently used a raspberry pi zero 2 w ( headless setup, 32-bit lite os ) to make a NAS with OMV and I wanted to use nextcloud then to obviously make a private cloud.

    After the omv setup and the NAS running well, I cannot do any command in the CLI like apt upgrade or update and more importantly i cant install nextcloud.

    I always get the same error each time about the public key not available.

    I went through dozen of post and page about this problem and none helped me.


    Here is the error for "sudo omv-upgrade" :


    Get:1 file:/var/cache/openmediavault/archives InRelease

    Ign:1 file:/var/cache/openmediavault/archives InRelease

    Get:2 file:/var/cache/openmediavault/archives Release

    Ign:2 file:/var/cache/openmediavault/archives Release

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Get:3 file:/var/cache/openmediavault/archives Packages

    Ign:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Get:3 file:/var/cache/openmediavault/archives Packages

    Get:4 file:/var/cache/openmediavault/archives Translation-en

    Ign:4 file:/var/cache/openmediavault/archives Translation-en

    Hit:5 http://deb.debian.org/debian bookworm-updates InRelease

    Get:6 http://httpredir.debian.org/debian bookworm-backports InRelease [56.5 kB]

    Hit:7 http://raspbian.raspberrypi.com/raspbian bookworm InRelease

    Get:8 http://security.debian.org/debian-security bookworm-security InRelease [48.0 kB]

    Hit:9 http://packages.openmediavault.org/public sandworm InRelease

    Hit:10 https://openmediavault.github.io/packages sandworm InRelease

    Get:11 http://archive.raspberrypi.com/debian bookworm InRelease [23.6 kB]

    Hit:12 https://cli.github.com/packages stable InRelease

    Ign:13 https://packages.ntop.org/apt-stable/bookworm_pi armhf/ InRelease

    Ign:14 https://packages.ntop.org/apt-stable/bookworm_pi all/ InRelease

    Err:15 https://packages.ntop.org/apt-stable/bookworm_pi armhf/ Release

    404 Not Found [IP: 2a03:b0c0:2:d0::d27:3001 443]

    Err:16 https://packages.ntop.org/apt-stable/bookworm_pi all/ Release

    404 Not Found [IP: 2a03:b0c0:2:d0::d27:3001 443]

    Err:6 http://httpredir.debian.org/debian bookworm-backports InRelease

    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131

    Err:8 http://security.debian.org/debian-security bookworm-security InRelease

    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8

    Err:11 http://archive.raspberrypi.com/debian bookworm InRelease

    The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E

    Reading package lists... Done

    E: The repository 'https://packages.ntop.org/apt-stable/bookworm_pi armhf/ Release' does not have a Release file.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

    E: The repository 'https://packages.ntop.org/apt-stable/bookworm_pi all/ Release' does not have a Release file.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

    W: http://deb.debian.org/debian/d…okworm-updates/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

    W: GPG error: http://httpredir.debian.org/debian bookworm-backports InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 0E98404D386FA1D9 NO_PUBKEY 6ED0E7B82643E131

    E: The repository 'http://httpredir.debian.org/debian bookworm-backports InRelease' is not signed.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

    W: http://raspbian.raspberrypi.co…dists/bookworm/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

    W: GPG error: http://security.debian.org/debian-security bookworm-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 54404762BBB6E853 NO_PUBKEY BDE6D2B9216EC7A8

    E: The repository 'http://security.debian.org/debian-security bookworm-security InRelease' is not signed.

    N: Updating from such a repository can't be done securely, and is therefore disabled by default.

    N: See apt-secure(8) manpage for repository creation and user configuration details.

    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://archive.raspberrypi.com/debian bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 82B129927FA3303E

  • chente

    Hat das Thema freigeschaltet.

    I even got error related to the public key, and the problem remain unsolved


    Error in web interface of omv for disable backports :

    Error for apt clean :

    Those ntop repos are outside the scope of OMV and you need to fix it or remove them.

    Nothing that OMV can take care of.


    Regarding the rest, post the output of:

    sudo omv-aptclean repos

    ls -al /etc/apt/sources.list.d/

    For "sudo omv-apt clean" :

    For "ls -al /etc/apt/sources.list.d/" :

    Code
    total 36
drwxr-xr-x  2 root root 4096 Mar 15 20:57 .
drwxr-xr-x 15 root root 4096 Mar 15 20:27 ..
-rw-r--r--  1 root root  121 Mar 15 18:03 github-cli.list
-rw-r--r--  1 root root  234 Mar 15 17:51 ntop.list
-rw-r--r--  1 root root  142 Mar 15 20:57 omvextras.list
-rw-r--r--  1 root root   60 Nov  1  2022 openmediavault-local.list
-rw-r--r--  1 root root  372 Mar 15 20:28 openmediavault-os-security.list
-rw-r--r--  1 root root  409 Mar 15 16:18 openmediavault.list
-rw-r--r--  1 root root  191 Mar 15 18:33 raspi.list


    The ntop part was a solution I found that supposedly fix the public key issue, but it didnt

    Zitat von Salade

    For "sudo omv-apt clean" :

    Post the complete output including the prompt, please.

    Here it is


    Zitat von Salade

    The ntop part was a solution I found that supposedly fix the public key issue, but it didnt

    Start by reverting what you did with it.

    No need to have outside repos that are being ignored and searching for them hit a 404 page.


    After, remove the lists that aren't there doing nothing:

    Zitat von Salade

    -rw-r--r-- 1 root root 121 Mar 15 18:03 github-cli.list

    -rw-r--r-- 1 root root 234 Mar 15 17:51 ntop.list


    This will reduce the errors leaving only 2 to deal with.


    Post the output of the rest of the lists:

    Code
    cat /etc/apt/sources.list
cat /etc/apt/sources.list.d/omvextras.list
cat /etc/apt/sources.list.d/openmediavault-local.list
cat /etc/apt/sources.list.d/openmediavault-os-security.list
cat /etc/apt/sources.list.d/openmediavault.list
cat /etc/apt/sources.list.d/raspi.list


    And the output of the gpg:

    sudo apt-key list


    Tomorrow I'll try to run a armhf Pi4 to see if I can figure out some things.

    Output of the lists :


    And here is the output of "sudo apt-key list" :



    I cannot thank you enough for taking your time to help me

    Zitat von Salade

    I've recently used a raspberry pi zero 2 w ( headless setup, 32-bit lite os )

    Can you explain in detail, all the steps you took?

    My Zero2W isn't prep and have no way to use it ATM so, I want to simulate what you did with a Pi4 to see if I can replicate your issue.


    I will try with the latest 32Bit version of Bookworm.


    On a side note, you should redo the steps but use the 64Bit version since it's supported by Zero2W:



    This will avoid ALL the issues you are having.

    I will list each step :

    1. Used Pi imager to setup the os ( 32 bit lite ) on the sd card of the raspberry pi

    2.Using ssh with my main pc I run sudo apt-get update and sudo apt-get upgrade -y ( it runs fine )

    3. I then install OMV using sudo wget -O - https://github.com/OpenMediaVault-Plugin-Developers/installScript/raw/master/install | sudo bash 

    I also used on my other try the same line but with install.sh, dont know if that change anything

    4.And then I do the usual thing when OMV is installed, changing password, sharing files, activating SMB, and setting user permission.


    I will try to use the 64-bit and report if the problem is solved

    Zitat von Salade

    I will try to use the 64-bit and report if the problem is solved

    Since you are using WiFi, better to skip the network on the script as instructed on the Github.

    When flashing the image, set the WiFi connection details on it, activate the SSH and fill the details for the USER and the HOSTNAME and LOCALE.

    You might lose SSH after reboot but it's only a matter of adding back the USER (on the OMV GUI) to the _ssh group:

    OpenMediaVault-Plugin-Developers/installScript: script that installs omv-extras and openmediavault if not installed already. (github.com)


    The 64-bit lite os version solved the problem !

    Right now I'm installing nextcloud without any issues related to public key. I tested beforehand if sudo omv-upgrade and sudo apt-get update worked and there was no error message like the one up there.

    Now I have sadly a issue during nextcloud's installation :

    I suppose I have to create another thread for this problem ?

    EDIT: i will beforehand do some research


    Also I'm using ethernet connection and SSH, USER, HOSTNAME and LOCALE were activated/filled by default because there were saved in Pi imager during my previous attempt.

    Zitat von Salade

    Now I have sadly a issue during nextcloud's installation

    The advice on the forum is to use it on docker.


    Installing it on the host might break things

    • Offizieller Beitrag
    Zitat von Salade

    Now I have sadly a issue during nextcloud's installation :

    Where did you get the idea to install Nextcloud on the OMV host?

    • Offizieller Beitrag
    Zitat von Salade

    During my research on the subject of OMV and Nextcloud I've seen on a video that said that this method was quicker and easier

    Interesting. It's the first time I've read something like this. I would like to see that video, could you post a link?

    Zitat von chente

    Interesting. It's the first time I've read something like this. I would like to see that video, could you post a link?

    Here is the link, the video is in french and the installation of Nextcloud is around 7min


    Externer Inhalt youtu.be
    Inhalte von externen Seiten werden ohne Ihre Zustimmung nicht automatisch geladen und angezeigt.
    Durch die Aktivierung der externen Inhalte erklären Sie sich damit einverstanden, dass personenbezogene Daten an Drittplattformen übermittelt werden. Mehr Informationen dazu haben wir in unserer Datenschutzerklärung zur Verfügung gestellt.

    • Offizieller Beitrag
    Zitat von Salade

    Here is the link, the video is in french and the installation of Nextcloud is around 7min

    Thanks for the link. I just watched the video and what it explains is how to install Nextcloud on the Raspberry operating system, at no point is openmediavault mentioned.


    You can go that route, but then you have to forget about openmediavault. They are not compatible, Nextcloud cannot be installed together with openmediavault. That's why we use docker. Docker allows you to do lightweight virtualization. That is, you run an operating system inside another operating system, so they do not interfere with each other. This explanation is very basic, it is only so that it is easily understood.


    The first thing is to learn how to use docker. You can read here and try installing some simple containers. https://wiki.omv-extras.org/doku.php?id=omv7:docker_in_omv


    After that you can install Nextcloud. You have two different paths in the forum.


    The first option is to install the linuxserver Nextcloud container with the Swag proxy. Many people use it on the forum and you will get a lot of support for problems. Here you have the guide. [How-To] Nextcloud with swag (Letsencrypt) using OMV and docker-compose


    The second option is the official Nextcloud AIO container together with Nginx Proxy Manager. This guide has been published for many months now and I have seen few problems on the forum since it was published. With the number of readings it has, I assume it is working well. RE: OMV Quick Configuration Guide


    Outside of that there are many other paths, from a virtual machine to other community containers. But in those cases you will have to look for support in other places outside the forum.

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden