My idea was a blind alley following this old thread.
Your proxy mode is 'none'. If it had been set to 'auto' we might have pursued it further.
My idea was a blind alley following this old thread.
Your proxy mode is 'none'. If it had been set to 'auto' we might have pursued it further.
Always make regular backups of your data (and test them).
Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.
If I were in your shoes I would jump out of this alligator pit and try Nautilus in a newly created guest user account to test if the same problems arise. Or even in Ubuntu in a fresh virtual machine in VirtualBox.
Always make regular backups of your data (and test them).
Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.
Another user with same problem .. but no answer ..
https://askubuntu.com/questions/1251...nsions-on-sftp
Another reference ..
https://linuxize.com/post/how-to-use...ransfer-files/
I would just use PuTTY client until this is solved. Law of diminishing returns applies.
Well spotted! I didn't find that in my searches. It seems that that person can connect, and only gets this error when accessing specific files. Whereas I get that error regardless when trying to connect in the first place.
Thanks. That's for CLI commands. I've managed to make the CLI commands work. It's only Nautilus that's giving me problems!
Well, I have FileZilla. I'll use that until I can get Nautilus to work. FileZilla is an excellent app, which usually does everything that I need, but for this specific host, Nautilus would be more convenient because of the workflow.
Always make regular backups of your data (and test them).
Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.
Actually, this link has proven useful. Comparing to other servers from the same host…
I can use the other servers without a problem from Nautilus. However, to access them, I need to give the correct starting directory, /home/[name]. E.g.
sftp://exa/home/mystart
But, the one that's giving me problems uses a virtual disk. The top-level directories within that virtual disk are directories from other servers (plural). I think that when Nautilus attempts to connect, it gets confused and fails.
It may be that this specific server just can't be used with Nautilus?
Always make regular backups of your data (and test them).
Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.
Do you have write permissions on that server?
Yes, I do. I can create, delete and modify files in it.
But.
Now that you mention it, in all of its subdirectories, yes, but not in the "root" (home).
That shouldn't make a difference, though, because I can still access the server through sftp or FileZilla, right? Nautilus must be accessing the server somehow differently from sftp and FileZilla.
Always make regular backups of your data (and test them).
Visit Full Circle Magazine for beginners and seasoned Linux enthusiasts.
Try this guide
And a further thought.
You wrote "I've managed to make the CLI commands work. It's only Nautilus that's giving me problems!"
Can you open terminal from within Nautilus (right click on folder, Open terminal here) and then apply terminal commands?
Last edited by dragonfly41; August 1st, 2021 at 04:53 PM. Reason: added new idea
Bookmarks