Hey,
So I’ve been connecting to an ftp server which I worked on with apps like GNOME Builder, and backed up the contents of with Pika Backup, connecting to it via the GNOME Files application, Nautilus, from the Network tab.
Recently, apps stopped being able to read files I opened with the file picker hosted on the ftp server, and after a lot of debugging I realised that was because Nautilus had for some reason switched from mounting the files under /run/user/1000/gvfs/ftp_address to the more abstract path ftp://ftp_address, under the virtual directory computer:///. Now apps can’t read those files as they are not mounted under an actual path.
I couldn’t find a way in Nautilus, FileZilla, or Dolphin to mount the ftp server files under a specified path /mnt/ftp_username, or even to put it back to the unwieldy but still working path it was under before, using a GUI.
I was recommended by an LLM assistant to use the curlftpfs command, but even with several variations of a command such as the following
sudo curlftpfs -v -o "uid=$UID,gid=$GID" ftp://username:correct%20password@ftp_address /mnt/ftp_username
it always gave the same error
Error setting curl:
I’m not sure what else to try, could I have some advice please?
Error setting curl:That doesn’t seem like a complete error message to me. Is there any more information? Maybe with the
-d(debug) flag?I know, right? But even with -d, -v, or -o debug, that’s all I get
Seems to be a known bug: https://github.com/curl/curl/discussions/14299
Hmm, that also says it should have been fixed last year
This bug is fixed in current master, set to be released in curl 8.10.0 on September 11, 2024.
Fixed in curl, but not in a curlftpfs, apparently. Look at the comments on the accepted answer.
Just as a test, don’t sudo, change to root and try it. Or, don’t sudo or change to root at all, and see if that will work.
Hmm, I did try that. It didn’t work, still same error.
Have you tried without the
ftp://part. eg.curlftpfs ftp-user:ftp-pass@my-ftp-location.local /mnt/my_ftp/I hadn’t, I just did, unfortunately it gives the same error.
