I sometimes use Dolphin and the URI fish:// to work with a SLES15SP4 host. This is a very comfortable way to edit a file or copy a file …
But now the connection is never established. My desktop openSUSE Leap 15.4 is able to connect to several hosts ((open)SUSE and other Distributions) but to a SLES15SP4 a connection is not possible. At the end I get the message ‘Folder is empty’.
I can reach this host via ssh and scp and I can mount a folder from there into my filesystem via mount.sshfs. But fish:// … no change.
BTW: sftp does not work, too.
Any hints? What is necessary to get this protocol running?
Normally, any attempts to access the home directory of the user “root”, regardless of local access attempts or, access attempts by means of network connections, are by default not allowed.
The same, usually, applies to the system directories …
Except when, and administrator, for whatever reason, adds the system directories to either the NFS exports list or, the exports list of any other server application …
I know of systems where, login to the user “root” and other system administration users, was allowed by means of the physical console terminal of the machine, which was physically separated from all the other machines in the computer room by means of a locked cage
The key to access that console was available only to a hand full of the administrators, despite the restricted access to the computer room plus, the restricted access to the building …
As long as scp with the user ‘root’ is possible it should be possible via fish …
And it is possible to SLES12SP5; RasPI, …
But a fresh SLES15SP4 installation makes trouble.
Please check, the KWallet entries for accessing the target host.
There may be something in ‘~/.cache/dolphin/qmlcache/’ – clean out that Cache directory.
It may be that, the stored Dolphin state is messed up – remove ‘~/.local/share/dolphin/dolphinstaterc’ and try again.