NZBget failed Categories

    • New
    • Official Post

    Thanks everybody for the time, i decide to stop with OMV, its perhaps to complicated for me.


    We going to buy a new Syology.


    Ron

    It's a shame seeing that you have been a member of the forum since 2021, but hey, everyone chooses the path they think is best for them. Good luck!

    • New
    • Official Post

    In my opinion you shouldn't give up, there is a lot of support on the forum. But if you're convinced that's what you want, I won't try to stop you, Synology isn't a bad option if you're looking for commercial software.

  • Could it be a folder permission issue? I created a test folder, and it works fine.


    First, I created a user and gave it sambashare permissions to enable use on Windows.


    Then, I went to Storage > Shared Folders to create a test folder named test-nzbget.


    I went to Services > SMB/CIFS > Shares to set up sharing for the test-nzbget folder, allowing me to see real-time changes on Windows.


    I went to Docker Hub to find NZBGet and copied the compose code, then modified it according to my own setup.

    The PUID and PGID can be found in User Management > Users.


    The key part is the volumes section. The /test-nzbget path is the Absolute Path copied from Storage > Shared Folders.


    /test-nzbget/config:/config means mapping /test-nzbget/config on the host machine to /config in the Docker container. This way, entering /config in NZBGet is equivalent to accessing /test-nzbget/config on the host. Similarly, /test-nzbget/downloads:/downloads works the same way; entering /downloads in NZBGet is equivalent to /test-nzbget/downloads on the host.


    Now, start NZBGet, and you’ll see it has created the config and downloads folders in /test-nzbget. The folders inside the downloads folder are also correctly mapped in the NZBGet settings, just like in the image below.


    Since I don't have a Usenet account, I used a regular download link for testing (at first, I thought it could download torrents, but it kept giving errors. After searching on Google and ChatGPT, I realized it can't :( ). It can download normally.


    So, I think the permissions for your folder or its parent folder might be incorrect, which is preventing NZBGet from writing. Please check the folder permissions using some commands or tools.


    At the same time, I have a few things to say about Synology. I recently switched from Synology to OMV. For most people, Synology is great, it has a more attractive GUI and simpler operation processes. However, there are some details that made me uncomfortable, such as slower transcoding with Jellyfin (I only noticed this after switching to OMV) and the fact that it uses a modified version of Btrfs. The reason I switched to OMV is that Synology did not detect bad sectors on my hard drive, which may be an isolated case. When I tried OMV, I saw the red bad sector (05) in the SMART options, which shocked me because that hard drive was only purchased six months ago. I initially thought it was an OMV issue since there were no errors on Synology. However, when I connected the hard drive to Windows, it also detected the 05 problem, and I realized it was a Synology issue. When I wanted to transfer data, I found out that Synology had modified the file system, making it unreadable by standard Linux. In short, after some operations, I transferred the data and sent the hard drive for warranty repair.

  • In my opinion you shouldn't give up, there is a lot of support on the forum. But if you're convinced that's what you want, I won't try to stop you, Synology isn't a bad option if you're looking for commercial software.

    Couldn't resist trying it again :)
    I tried it with OMV today anyway, and I got it working, via a explanation on the internet, it was indicated to create a user for docker,

    followed this and NZBget retrieves and places it in the folders, movies, series etc.
    Only I run into the problem that I am not allowed to delete the files. the docker user dockeruser must me..... ??




    • New
    • Official Post

    I would say that you need to understand a little more about how Docker works. I suggest you take a look at this section https://wiki.omv-extras.org/do…ker_in_omv#what_is_docker


    The summary is that volumes are folders on the host that the container uses as its own. So it doesn't make sense to configure the same folder on the host for two different folders in the container. You must set a different path for each folder.


    The explanation in Zafkiel 's post is very detailed and I think it can help you. In short, in your case I think I would make a new folder, make sure that the container user has write permissions to that folder.


    Another detail. It is more than enough that the users dockeruser and ron belong to the users group. You should remove them from all other groups.

  • Only I run into the problem that I am not allowed to delete the files. the docker user dockeruser must me..... ??

    Exactly how are you trying to delete the files? Be very specific with your answer.


    What I have always done, is to have an ordinary user (fred:users) on the system that I use when I need shell access or remote access to OMV. And I run all my dockers as that user.


    Edit:


    Something that you can try quickly is to place this into the environment section of your compose file and restart the container:

    Code
    - UMASK=0000

    Worth a try, but it might not work.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    Edited 3 times, last by gderf ().

  • Another detail. It is more than enough that the users dockeruser and ron belong to the users group. You should remove them from all other groups.

    It has been my experience that if an ordinary user wants to run docker commands as that user in the shell and not have to have root privileges via su, then that user needs to be in the docker group.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • Hi Zafkiel, thanks for your time to make this explanation, It's working, its downloading and its place it to the right folder.

    I have only now that I cannot remove the content after it.

    If I look on WINSCP is the owner of the NZB folder 911 ?

    Do you know how its be done? and how I can change it the bv Root?


    As you can see must the docker file wright, also the UID from my als user





    services:

    nzbget:

    image: lscr.io/linuxserver/nzbget:latest

    container_name: nzbget

    environment:

    # - PUID=

    # - PGID=

    - TZ=Europe/Amsterdam

    - NZBGET_USER=nzbget #optional

    - NZBGET_PASS=tegbzn6789 #optional

    volumes:

    - /data/nzbget/data:/config

    - /srv/dev-disk-by-uuid-c90882d1-0d82-43e2-a879-c3a0b9019dbe/Nas/Nzbget:/downloads



    ports:

    - 6789:6789

    restart: unless-stopped







    Ron

  • Why did you comment out the PUID and PGID statements in your compose file? That's a big mistake.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • # - PUID=

    # - PGID=

    Based on my tests, when you use the linuxserver/nzbget image and comment this out, after starting NZBGet, the file permissions are set to 911. This may be due to linuxserver virtualizing a system and running Docker within it, as there is no such issue with other NZBGet images. Of course, setting PGID and PUID is still recommended.

  • Based on my tests, when you use the linuxserver/nzbget image and comment this out, after starting NZBGet, the file permissions are set to 911. This may be due to linuxserver virtualizing a system and running Docker within it, as there is no such issue with other NZBGet images. Of course, setting PGID and PUID is still recommended.

    :( But do know how you can remove the content?

  • Oh, I found a problem. If the set PUID user is not the SMB login user, SMB will not have write permissions... I'm still testing.

    I got it! Need to add the following statement under the environment in the compose file.

    Code
    - UMASK=002

    In this way, the files downloaded by NZBGet have 0664 permissions and can be read and written by users with the same GID


    Addendum: GID must be set, otherwise linuxserver/nzget image defaults to 911 groups, and OMV's 100 groups cannot be written. It's okay not to set UID, but GID must be set. (Nevertheless, it is still recommended to set GID and UID)

  • I got it! Need to add the following statement under the environment in the compose file.

    Code
    - UMASK=002

    In this way, the files downloaded by NZBGet have 0664 permissions and can be read and written by users with the same GID


    An even "looser" suggestion was previously made, but either not read or read and ignored.


    It is also possible to set UMASK within the NZBget application in Settings | Security.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    • New
    • Official Post

    It has been my experience that if an ordinary user wants to run docker commands as that user in the shell and not have to have root privileges via su, then that user needs to be in the docker group.

    This is not correct. I also thought the same thing as you years ago but that's not the case.

    Zoki published a long time ago that including the user who runs the container in the docker group is a security flaw. Allows an attacker to escalate permissions and access the server. In fact he said that he sometimes did it himself in the company where he worked :)

    Since then I always configure appuser only in the users group (and render and video for transcoding) and I have never had any problems.

Participate now!

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