Good evening, has anyone had the need to perform an upload on an nfs? I'm changing the application to use a network mapping for the upload, but lucee doesn't accept me putting //<ip>/folder or the mapped drive on the server: F:/folder/

Can you elaborate on "doesn't accept"? Do you get an error? Does nothing happen? Does an avatar of Zack pop up and go "nah mate, and then sing waltzing matilda" (hate it when I get those errors)? How are you creating the mapped drive? These are generally user-specific, and Lucee will likely not be running as the same user that you are... I think perhaps yer short on some info here...

Good morning @Adam Cameron tks you reply, On the main server, NFS was configured as a disk drive, D:/shares On the secondary servers, a network mapping was created pointing to the main server, //<ip>/shares and they created a mapping in windows for this address. The first difficulty was to make iis display the PDFs that were on this NFS, on the main server it was enough to add the windows user IISUS in the NFS permissions, on the other servers I had to change the user running IIS to be able to access the files. The problem now is about the upload, on the main server where the NFS is there are no problems. But in others when I try to upload using the network path or the windows mapping, the cffile returns non-existent directory. I researched last night about some possibilities, among them it says to upload locally and perform a cfftp to the other server, but that would involve uploading an FTP service which would not be easy. Is there any way to make the cffile able to upload to the remote server?

Depending on how you mount your NFS share, and the version of your NSF server, troubleshooting is 'FUN'. I would first take a look at your main server and make sure you have patched and updated your NFS library to the very latest version. I would check to see if there are any bug reports, as I have found there usually are multiple. Second, I would look at possibly using something else other than NSF protocol for file upload, for the reasons above. SCP has better performance and is far less prone to error. We use SSHFS, which is a free utility to allow windows servers to mount remote UNIX/LINUX directories. Another option, rsync, which can be used in conjunction with any supported third-party protocol or binary, you could even use blob HTTP puts

It's really been a lot of fun :p At first the main server is OK, the problem is not to upload the server, but to make the application that is in Lucee carry out this upload to a remote directory

@Victor B Vieira you talk about configuring IIS for the correct perms to access the network storage, but at no point do you mention Lucee. It's not IIS doing the file operations to the network storage; it's Lucee. The client uploads the file to IIS, and IIS sticks it in a temp dir. after that, it's Lucee doing all the work.

I think this is exactly my problem I don't know where to change in lucee, so that it can access the remote directory :s I found some information about changing a Tomcat config file, but I tried to put the network user that has access to the directory and it didn't work

It's not to do with Lucee. It's to do with file system permissions. Same as you did for the IIS user ("it was enough to add the windows user IISUS in the NFS permissions"), you need to do with the user Lucee is running as (might be Tomcat, dunno).

ok, i will study how to change, tks 😉

Sorry to seem vague but I'd need to look it up tool; and you'd still have to afterwards anyhow.

no problem XD