I can't install plugins

  • I changed the mirrors, but now I have the GPG key error, I searched the forum, but I still haven't found a way to solve it


    Reading package lists...
    W: GPG error: https://mirror.nju.edu.cn/open…iavault-plugin-developers sandworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 326A835E697B890A
    E: The repository 'https://mirror.nju.edu.cn/openmediavault/openmediavault-plugin-developers sandworm InRelease' is not signed.

    1: OMV 7 / CPU - J2900 / RAM - 8GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, CUPS, pyKMS, Syncthing, Transmission e Watchtower


    2: OMV 7 / CPU - J2900 / RAM - 16GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, Jackett, Plex, Tautulli, Transmission e Watchtower

  • I ran the command and it still doesn't give me the same error, I'm now trying to re-enable IPv6 to try to use it on the default mirror, since IPv6 was not blocked on the ISP

    1: OMV 7 / CPU - J2900 / RAM - 8GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, CUPS, pyKMS, Syncthing, Transmission e Watchtower


    2: OMV 7 / CPU - J2900 / RAM - 16GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, Jackett, Plex, Tautulli, Transmission e Watchtower

    • Official Post

    I'm now trying to re-enable IPv6 to try to use it on the default mirror, since IPv6 was not blocked on the ISP

    As I mentioned previously, github pages (where the omv-extras repo is located) does not listen on ipv6.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.5 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • I changed the mirrors, but now I have the GPG key error, I searched the forum, but I still haven't found a way to solve it


    Reading package lists...
    W: GPG error: https://mirror.nju.edu.cn/open…iavault-plugin-developers sandworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 326A835E697B890A
    E: The repository 'https://mirror.nju.edu.cn/openmediavault/openmediavault-plugin-developers sandworm InRelease' is not signed.

    I've encountered this issue before, but I kind of forgot how I solved it. Anyway, check if there's an omvextras.gpg file under /usr/share/keyrings and see if its size is 0KB. If it's 0KB, you can try this command:

    Code
    wget -qO - https://mirror.nju.edu.cn/openmediavault/openmediavault-plugin-developers/omvextras2026.asc | sudo gpg --dearmor -o /usr/share/keyrings/omvextras.gpg

    OMV 7.x | 6.8 Proxmox Kernel

    GIGABYTE Z370M DS3H Motherboard

    Intel G4560 CPU | 16G×1 Non-ECC RAM

    128G SSD + 1T SSD + 4T×2 HDD | No RAID

    500W ATX PSU | APC BK650-CH UPS

    • Official Post

    I've encountered this issue before, but I kind of forgot how I solved it. Anyway, check if there's an omvextras.gpg file under /usr/share/keyrings and see if its size is 0KB. If it's 0KB, you can try this command:

    sudo omv-aptclean repos should do that.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.5 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • As I mentioned previously, github pages (where the omv-extras repo is located) does not listen on ipv6.

    I don't know how, but here I enabled IPv6 in DHCP in the OMV network settings and run the apt clean command previously posted and it worked, I'm now able to install the openmediavault-remotemount that I wanted since the beginning of this saga, I'll post the result the apt clean below and the remote mount installation.


    These were the errors that presented using IPv6, after enabling in OMV they no longer appeared:

    Cannot initiate the connection to openmediavault-plugin-developers.github.io:443 (2606:50c0:8001::153). - connect (101: Network is unreachable) Cannot initiate the connection to openmediavault-plugin-developers.github.io:443 (2606:50c0:8002::153). - connect (101: Network is unreachable) Cannot initiate the connection to openmediavault-plugin-developers.github.io:443 (2606:50c0:8000::153). - connect (101: Network is unreachable) Cannot initiate the connection to openmediavault-plugin-developers.github.io:443 (2606:50c0:8003::153). - connect (101: Network is unreachable)


    The commands were now executed on my OMV 1, which hadn't changed anything regarding repositories or mirrors, I'm going to revert the settings on my OMV 2 and try to do the same thing I did on OMV 1.

    • Official Post

    These were the errors that presented using IPv6, after enabling in OMV they no longer appeared:

    Maybe they do listen on ipv6 now. I don't have a good way to test.

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.5 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Maybe they do listen on ipv6 now. I don't have a good way to test.

    Probably yes, I also have no idea how to do these tests, but I'm glad it worked

    1: OMV 7 / CPU - J2900 / RAM - 8GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, CUPS, pyKMS, Syncthing, Transmission e Watchtower


    2: OMV 7 / CPU - J2900 / RAM - 16GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, Jackett, Plex, Tautulli, Transmission e Watchtower

  • Thank you to everyone who took the time to come to this topic to help, I appreciate everyone.

    1: OMV 7 / CPU - J2900 / RAM - 8GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, CUPS, pyKMS, Syncthing, Transmission e Watchtower


    2: OMV 7 / CPU - J2900 / RAM - 16GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, Jackett, Plex, Tautulli, Transmission e Watchtower

  • One more question, how do I revert these repository mirrors to the defaults, I managed to revert some by editing some .list, but not all of them returned to the default.

    Code
    omv-env set OMV_APT_REPOSITORY_URL "https://mirror.nju.edu.cn/openmediavault/public"
    omv-env set OMV_APT_ALT_REPOSITORY_URL "https://mirror.nju.edu.cn/openmediavault/packages"
    omv-env set OMV_APT_KERNEL_BACKPORTS_REPOSITORY_URL "https://mirror.nju.edu.cn/debian"
    omv-env set OMV_APT_SECURITY_REPOSITORY_URL "https://mirror.nju.edu.cn/debian-security"
    # 如果你有安装 omv-extras 则需要运行如下命令更改源
    omv-env set OMV_EXTRAS_APT_REPOSITORY_URL "https://mirror.nju.edu.cn/openmediavault/openmediavault-plugin-developers"
    omv-env set OMV_DOCKER_APT_REPOSITORY_URL "https://mirror.nju.edu.cn/docker-ce/linux/debian"
    omv-env set OMV_PROXMOX_APT_REPOSITORY_URL "https://mirror.nju.edu.cn/proxmox/debian"
    # 使得环境变量更改生效
    omv-salt stage run all

    1: OMV 7 / CPU - J2900 / RAM - 8GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, CUPS, pyKMS, Syncthing, Transmission e Watchtower


    2: OMV 7 / CPU - J2900 / RAM - 16GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, Jackett, Plex, Tautulli, Transmission e Watchtower

    • Official Post

    how do I revert these repository mirrors to the defaults, I managed to revert some by editing some .list, but not all of them returned to the default.

    The easiest way is to delete the relevant entries in /etc/default/openmediavault

    omv 8.0.10-2 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.5 | compose 8.1.3 | cterm 8.0 | borgbackup 8.1.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • The easiest way is to delete the relevant entries in /etc/default/openmediavault

    It worked, now everything seems to be ok, thanks

    1: OMV 7 / CPU - J2900 / RAM - 8GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, CUPS, pyKMS, Syncthing, Transmission e Watchtower


    2: OMV 7 / CPU - J2900 / RAM - 16GB

    Plugins: omvextrasorg, compose, cputemp, filebrowser, flashmemory, mergerfs, remotemount, sharerootfs e wetty.

    Docker: Portainer, Heimdall, Jackett, Plex, Tautulli, Transmission e Watchtower

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!