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.
services:
nzbget:
image: lscr.io/linuxserver/nzbget:latest
container_name: nzbget
environment:
- PUID=1000
- PGID=100
- TZ=Asia/Shanghai
- NZBGET_USER=test
- NZBGET_PASS=test
volumes:
- /test-nzbget/config:/config
- /test-nzbget/downloads:/downloads
ports:
- 6789:6789
restart: unless-stoppedq
Display More
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.
