Beiträge von Soma

    Forgot to mention that I also followed another post and added the following commands under environment:

    Post the link to the post where you saw that, please.

    Those envs don't exist on the linuxserver image.

    Remove them.

    - PUID=${PUID}

    - PGID=${PGID}

    Where is this env set?

    I find it better to use the proper number.

    Run on CLI id appuser and use that number. Should be 1000 or bigger, depending how many users you created.

    Same goes for GID. In your case will be 100.

    Code
    - PUID=1000 # Or 1001, or 1002, etc
    - PGID=100


    Since you didn't set a DATA volume, your data is volatile.

    You don't want that and need to have the volume on a seperate drive.


    You should start fresh and follow the guide proper because it is mentioned there:

    Code
          - /srv/dev-disk-by-label-disk1/appdata/nextcloud/data:/data     #/srv/dev-disk-by-label-disk1 needs to be adjusted


    Your YML should be something like:


    Where is the data folder that is used when setting up NC?

    Post the YML used but omit sensible INFO (password, email, url, etc)

    2. How can I increase the upload file size limit?

    Did you restarted nextcloud after editing that file?

    And how did you edit it?

    Which permissions are on the HOST php-local.ini file?

    It has to be owned by the UID:GID that is on the YML.



    And what shows on the Nextcloud System Page?


    I don't see that file being used on OMV7:

    openmediavault/deb/openmediavault/usr/share/openmediavault/engined/inc at master · openmediavault/openmediavault (github.com)


    The date shows // 2016-01-17 19:34:29,266:DEBUG:letsencrypt.cli:Picked account: <Account(eb49da97b040939e9439a6a1c123294c)>


    And OMV doesn't use letsencrypt ( and never did, AFAIK)

    Maybe a leftover from previous versions?


    For now, move that file out of there and restart engined

    You posted only the output but also post the commands prompt.

    I assume you are using root to run them.
    mv /usr/share/openmediavault/engined/inc/90letsencrypt.inc /root/


    systemctl restart openmediavault-engined


    systemctl status openmediavault-engined

    The output is too long, so I attached it as a file

    You have some errors on the output, although none serious:

    Code
    W: http://adelolmo.github.io/bullseye/dists/bullseye/InRelease: Key is stored in legacy trusted.gpg keyring (/etc/apt/trusted.gpg), see the DEPRECATION section in apt-key(8) for details.

    I don't know what you have done or installed but that repo isn't part of OMV nor is updated to use bookworm.

    Either change it if you need it and it exists for bookworm, or delete it.


    Code
    No diversion 'any diversion of /usr/sbin/omv-mkaptidx', none removed.
    Rebuild apt index ...
    bash: line 85: omv-mkaptidx: command not found

    This shouldn't happen.


    sudo wget -O /usr/sbin/omv-mkaptidx https://github.com/openmediavault/openmediavault/raw/master/deb/openmediavault/usr/sbin/omv-mkaptidx


    sudo chmod +x /usr/sbin/omv-mkaptidx


    sudo omv-mkaptidx



    Will continue in a while since I have to get out of work.

    The only issue that I have left is that the GUI of the updates page remains empty, even after refreshes and getting an email from apticron that updates are available. Does anyone here know how to fix this?

    That's not an issue per se. It's only awkward.

    apticron runs and detects that are updates and sends the mail informing it.

    GUI doesn't know because the info it gets, is from cron that runs (in my time zone, don't know if it's general) at 7am.

    Only then, it will show up on the GUI.


    You can confirm the above by:

    receive an email from apticron informing that there are updates available.

    Wait till next day morning or lunch (if on UTC) and see if updates show on the GUI (they will).

    Update from GUI.


    To make them shown on the GUI immediately, after apticron, you need to click the magnifying lens on the update manager GUI page, not refresh.

    like this?

    No. That way, you are moving the tv-shows folder and rename it ToDo inside /srv/mergerfs/Media/


    What you want is to move files that are inside tv-shows and have them inside the ToDo folder, correct?

    Code
    mv /srv/dev-disk-by-uuid-ebc5282d-580c-4b97-ba3b-5b1beba70312/Leeching/Leeching-Done/tv-shows/* /srv/mergerfs/Media/Media/ToDo/

    You better read about the mv command since it doesn't have the same flags as rsync.

    mv(1): move files - Linux man page (die.net)


    Try first with 1 file and check if permissions are maintained.

    Code
    mv -v /srv/dev-disk-by-uuid-ebc5282d-580c-4b97-ba3b-5b1beba70312/Leeching/Leeching-Done/tv-shows/<A FILE NAME.MKV> /srv/mergerfs/Media/Media/ToDo/
    
    ls -al /srv/mergerfs/Media/Media/ToDo/