I have one of those mini fanless mini PC boxes with Proxmox and pfsense installed. Jellyfin has been installed as a lxc via one of the helper scripts. Set it up and it works fine.

I'm now trying to set it up to access an old Netgear ReadyNAS NV+ that I have lying around. It's been setup with SMB/CIFS as well as FTP access. I'm considering disabling SMB/CIFS access since I think I don't need that anymore. I think the NAS only supports TLS 1.2 protocol and it's probably safer to disable it security wise. After searching around, I've come across curlftpfs which seems to be able to mount a ftp server as a local directly which i can then use as a library for jellyfin.

Is this the best way or is there a better alternative I can consider?

Thanks.

top 10 comments

sorted by: hot top controversial new old

[–] [email protected] 0 points 8 months ago (1 children)

CIFS is probably more robust than curlftpfs, but I'd probably just go full NFS on it if you care about performance.

[–] [email protected] 0 points 6 months ago

I ended up mounting the NAS share via CIFS and it appears to be working.

[–] [email protected] 0 points 8 months ago

I’ve never even heard of curlftpfs, but I can’t think of a reason why it wouldn’t work. You should try it out and let us know… I tried NFS once and didn’t like it.

[–] [email protected] 0 points 8 months ago (2 children)

Why don't you try NFS? For me it's a lot easier to set up...

[–] [email protected] 0 points 6 months ago (1 children)

I tried to mount the share as NFS, but it didn't seem to work from the console in the container. I ended up using CIFS which worked.

[–] [email protected] 0 points 6 months ago (1 children)

Probably the container does not have the required NFS client/libraries, but you don't have to do this inside the container... You mount it on the host and share it via a docker volume with the container.

[–] [email protected] 0 points 6 months ago (1 children)

I have installed nfs-kernel-server packages. I think it is possibly a permissions issue.

I briefly considered mounting it on the host (Proxmox) layer, but the way I have things set up, I only power on the NAS if I need to access it. Most of the time the Proxmox hardware will be booting up when the NAS is off and I think it will cause boot issues trying to mount a NAS share which it cannot find.

[–] [email protected] 0 points 6 months ago (1 children)

Remember that the container sits on a different network, the docker network, maybe that's why access doesn't work.

You can add the mount to be noauto in fstab, so it doesn't mount it unless you access the location. You can also mount it manually or via script, as needed.

Not sure how to help more, you have a peculiar setup...

[–] [email protected] 0 points 6 months ago

"noauto" sounds like a step in the right direction. I might give it a shot.

Many thanks. You've been very helpful.

[–] [email protected] 0 points 8 months ago

Because insecure FTP access is already enabled on the NAS ;-)