Posts by Thormir84

    I've been using it for a while and haven't encountered any issues with its operation.

    I don't know if it makes a difference, but i don't use volumes; i simply bound it to a folder.

    Try copying my compose exactly as it is, modifying the "volumes" variables to always point to the same folder.


    At this very moment, i have OMV 8.0.5-2 with kernel 6.17.4-2-pve; everything was updated starting from OMV 7, as mentioned at the beginning of this thread. I checked whether DKMS and ZFS-DKMS were installed by running the "apt remove" command, and both are missing. This is probably a result of the omv-extras update that was necessary to proceed with the upgrade.

    Thanks, i had imagined something like that; what i don't understand is why it was proposed as an update. Anyway, just don't set it as the boot kernel and there won't be any problems.

    This morning i found an update for the OMV kernel, called 6.17.8+deb13-amd64; the problem is that if i install it and boot OMV with it, ZFS no longer works.

    Is anyone else experiencing this?

    For now, I'm sticking with 6.17.4-1-pve.

    I tried to install kernel 6.14.11-4-pve; the installation gave me some errors related to ZFS, probably linked to the failed installation of the openmediavault-zfs plugin. At this point, via CLI, i ran "apt remove openmediavault-zfs" and immediately after, "apt autoremove" to remove all dependencies.


    After completing this procedure, i reinstalled kernel 6.14.11-4-pve via the web GUI, which this time succeeded; i rebooted the VM and tried to install the ZFS plugin again. This time, the installation was successful, and everything seems to be working correctly.


    At this point, i would say that to perform the migration from OMV 7 to 8 on a machine with a Proxmox kernel and ZFS plugin, it is necessary to first remove the ZFS plugin, update, install the new kernel for Debian 13, and then proceed with the installation of the ZFS plugin once everything else is done.


    We just need to understand if there could be any consequences for existing data and folders.

    I tried, with a new test VM, to install only OMV7, the updates, and the kernel plugin. I set the pve kernel and, without doing anything else, ran the upgrade command. The operation, this time, was successful; everything updated correctly. At this point, I installed the plugin "openmediavault-zfs 8.0.1"; however, the operation was not successful and returned the same errors that occur during migration from 7 to 8 when the ZFS plugin is already installed.

    Premise: I use OMV as a VM on Proxmox, updated to version 9.1.2.


    OMV is updated to version 7.7.24-3 with kernel 6.14.8-3-bpo12-pve.


    Docker is installed.


    The plugins in use on OMV are:

    openmediavault-ftp 7.0.2-1

    openmediavault-kernel 7.1.13

    openmediavault-nut 7.0.10-1

    openmediavault-omvextrasorg 7.0.5

    openmediavault-resetperms 7.1.1

    openmediavault-sharerootfs 7.0-1

    openmediavault-zfs 7.1.4.


    Yesterday, as a test, i tried to upgrade it to OMV 8 using the command omv-release-upgrade; the operation seemed to proceed without problems but ended with some errors related to ZFS.

    I restarted the NAS to see if there were any issues, and it apparently started up correctly, except that it is no longer possible to access the web GUI due to a "502 - bad gateway" error.

    After restoring a previous backup of the VM, i set up a new one from scratch; i installed OMV 7, applied all updates up to the latest, and installed the kernel plugin to be able to use the same kernel as the original VM.

    At this point, i installed the plugin for ZFS and, without doing anything else, i ran the command to upgrade from 7 to 8; just like the first time, on the other VM, at some point it reports problems with ZFS and stops.

    Restarting the system, everything seems to start, and, like the first time, it is no longer possible to access the web GUI due to the error "502 - bad gateway".

    You have custom. How did you handle this, to access your web from LAN?

    Are you referring to how to reach the custom domain when i am on the same LAN as the destination?

    So, at home, when i had everything connected to the Fritzbox 7950 router, it simply worked without extra rules; the same thing has been true since i set up an OPNsense firewall in a VM.

    I just had to expose the WAN of the firewall through the Fritzbox and configure the NAT rules to OPNsense.

    At the office, on the other hand, i have an Endiam UTM firewall; for the custom domain to be reachable from the LAN with this firewall, it is necessary to set up source NAT rules that point to the host machine.

    I have no idea how it works in other cases; my experience is currently limited to the situations i have listed.

    So, for everything to work, the following settings are necessary:


    APACHE_IP_BINDING: HOST_IP


    If you have problems with 127.0.0.1 or 0.0.0.0, use the host's IP; for example, if the server running Docker is 192.168.10.33, then this is the IP you need to enter.


    As for NGINX, port 11000 is correct, but you need to use http and not https.


    For example, you will have:


    http://192.168.10.33:11000


    On the router, ports 80 and 443 must be forwarded to NGINX to the ports you set in the compose.


    In my case, for example, in the compose I set:


    8484:80

    8443:443


    So on the router it will be:


    PUBLIC 80 -> LOCAL 8484

    PUBLIC 443 -> LOCAL 8443

    You need to mount the folder where the photos are located as a volume; the correct syntax is:


    Code
    volumes:
    - /mnt/nas_docker_dati/immich/upload:/data #this is where the backup photos from the app on the smartphone end up
    - /mnt/nas_foto/Marco/Foto:/photos/marco:ro #this is one of the folders with photos already present on the NAS


    Once the folder is mounted, you need to log into Immich with the admin account and go to the 'administration' -> 'external libraries' section and add the photos.



    Honestly, I wouldn't know how to help you; I also use OPNsense as a firewall (as a VM on KVM), but to avoid strange setups or issues like yours, I bought a 4-port ethernet card and associated it with the VM via passthrough.


    GLOTRENDS ST7419 Scheda di rete Ethernet RJ45 a 4 porte da 2,5G compatibile con controller Intel 1226, interfaccia PCIE 3.0 X4, supporto Windows 11/10/Windows Server/Linux/ESX/VMware ESXi
    Scheda di rete ethernet RJ45 a 4 porte da 2,5Gb (controller Intel 1226), interfaccia PCIe 3.0 X4, negoziazione automatica delle connessioni a velocità…
    www.amazon.it