Hi,
I use dolphin every day to connect to multiple accounts on different servers using SFTP. (It’s very easy and convenient to me working that way.) Unfortunately from yesterday on, dolphin refuses to connect to any account on certain server, returning username/password prompt over and over, like they are wrong. The credentials are fine. I’m connecting successfully using SSH in console and by SFTP using Filezilla, or even Nautilus.
Even funny to me is the fact dolphin connects successfully to other my servers, but not this particular.
I tried from Manjaro LiveCD and it connects everywhere - everything is OK. From different Manjaro PC - also OK.
But not from my current installation.
I even uninstalled dolphin and installed it again. Nothing change.
Is there some kind of cache, or something I can reset? I know if I reinstall OS, the problem will be gone, but I really don’t want to do this.
Hi @nickoloff, and welcome!
Only thing regarding that I can think of is clearing your users’ cache:
rm -rf ~/.cache/*
Maybe followed by rebooting.
Edit:
It might also have been the servers’ signature has changed, I think. Try removing it from:
~/.ssh/authorized_keys
Or just remove it and it’ll be recreated:
mv ~/.ssh/authorized_keys ~/.ssh/authorized_keys.backup
You are right! It’s on user level. I created new user account logged in and everything is fine from there.
I should delete .cache folder. Is it safe deleting all the content or I can solve the problem with certain folders?
If you delete the content it should not be a problem.
(I don’t know what will happen, if anything, should you delete the directory as well.)
Verify the type of encryption used for key exchange.
Try connecting using the konsole app
ssh -v <server>
You can safely delete it.
The whole folder with all it’s contents.
What is needed will be recreated.
rm -rf ~/.cache
Of course not, because reinstalling an application does not change anything to the configuration files in the individual users’ home directories. And that’s where your problem lies.
I would recommend renaming dolphin’s configuration files under ~/.config and ~/.local/share while dolphin is not running, and then starting and reconfiguring dolphin.
Rebooting is not necessary, but deleting the cache must be done from a tty while completely logged out of Plasma. Otherwise there’s no point, as Plasma will simply save its faulty configuration again to the same cache files.
Hi Aragorn,
I deleted:
~/.config/dolphinrc
~/.local/share/dolphin
and the content of ~/.cache from tty. Logged out of Plasma.
Reboot. The files are recreated, but the problem still remains.
Did you log out of Plasma before deleting those files?
Then perhaps something is amiss with the files in your ~/.ssh/ — see @Mirdarthos’ comment higher up.
Here is the output:
debug1: OpenSSH_10.2p1, OpenSSL 3.6.1 27 Jan 2026
debug1: Reading configuration data /home/user/.ssh/config
debug1: /home/user/.ssh/config line 6: Applying options for dm
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Reading configuration data /etc/ssh/ssh_config.d/20-systemd-ssh-proxy.conf
debug1: Reading configuration data /etc/ssh/ssh_config.d/30-libvirt-ssh-proxy.conf
debug1: Connecting to dm [188.138.29.236] port 22.
debug1: Connection established.
debug1: no pubkey loaded from /home/user/.ssh/id_rsa
debug1: identity file /home/user/.ssh/id_rsa type -1
debug1: no identity pubkey loaded from /home/user/.ssh/id_rsa
debug1: no pubkey loaded from /home/user/.ssh/id_ecdsa
debug1: identity file /home/user/.ssh/id_ecdsa type -1
debug1: no identity pubkey loaded from /home/user/.ssh/id_ecdsa
debug1: no pubkey loaded from /home/user/.ssh/id_ecdsa_sk
debug1: identity file /home/user/.ssh/id_ecdsa_sk type -1
debug1: no identity pubkey loaded from /home/user/.ssh/id_ecdsa_sk
debug1: no pubkey loaded from /home/user/.ssh/id_ed25519
debug1: identity file /home/user/.ssh/id_ed25519 type -1
debug1: no identity pubkey loaded from /home/user/.ssh/id_ed25519
debug1: no pubkey loaded from /home/user/.ssh/id_ed25519_sk
debug1: identity file /home/user/.ssh/id_ed25519_sk type -1
debug1: no identity pubkey loaded from /home/user/.ssh/id_ed25519_sk
debug1: Local version string SSH-2.0-OpenSSH_10.2
debug1: Remote protocol version 2.0, remote software version OpenSSH_9.6p1 Ubuntu-3ubuntu13.14
debug1: compat_banner: match: OpenSSH_9.6p1 Ubuntu-3ubuntu13.14 pat OpenSSH* compat 0x04000000
debug1: Authenticating to dm:22 as 'onboard'
debug1: load_hostkeys: fopen /home/user/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: sntrup761x25519-sha512@openssh.com
debug1: kex: host key algorithm: ssh-ed25519
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: SSH2_MSG_KEX_ECDH_REPLY received
debug1: Server host key: ssh-ed25519 SHA256:+dvW7NqBMZ0lCHzkPOOaEDdhvEMcBV44R2JpmMlqWQ0
debug1: load_hostkeys: fopen /home/user/.ssh/known_hosts2: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or directory
debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or directory
debug1: Host 'dm' is known and matches the ED25519 host key.
debug1: Found key in /home/user/.ssh/known_hosts:54
debug1: ssh_packet_send2_wrapped: resetting send seqnr 3
debug1: rekey out after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: Sending SSH2_MSG_EXT_INFO
debug1: expecting SSH2_MSG_NEWKEYS
debug1: ssh_packet_read_poll2: resetting read seqnr 3
debug1: SSH2_MSG_NEWKEYS received
debug1: rekey in after 134217728 blocks
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug1: kex_ext_info_check_ver: publickey-hostbound@openssh.com=<0>
debug1: kex_ext_info_check_ver: ping@openssh.com=<0>
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: SSH2_MSG_EXT_INFO received
debug1: kex_ext_info_client_parse: server-sig-algs=<ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25519@openssh.com,sk-ecdsa-sha2-nistp256@openssh.com,rsa-sha2-512,rsa-sha2-256>
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Will attempt key: /home/user/.ssh/id_rsa
debug1: Will attempt key: /home/user/.ssh/id_ecdsa
debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk
debug1: Will attempt key: /home/user/.ssh/id_ed25519
debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk
debug1: Trying private key: /home/user/.ssh/id_rsa
debug1: Trying private key: /home/user/.ssh/id_ecdsa
debug1: Trying private key: /home/user/.ssh/id_ecdsa_sk
debug1: Trying private key: /home/user/.ssh/id_ed25519
debug1: Trying private key: /home/user/.ssh/id_ed25519_sk
debug1: Next authentication method: password
onboard@dm's password:
Authenticated to dm ([188.138.29.236]:22) using "password".
debug1: channel 0: new session [client-session] (inactive timeout: 0)
debug1: Requesting no-more-sessions@openssh.com
debug1: Entering interactive session.
debug1: pledge: filesystem
debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
debug1: client_input_hostkeys: searching /home/user/.ssh/known_hosts for dm / (none)
debug1: client_input_hostkeys: searching /home/user/.ssh/known_hosts2 for dm / (none)
debug1: client_input_hostkeys: hostkeys file /home/user/.ssh/known_hosts2 does not exist
debug1: client_input_hostkeys: host key found matching a different name/address, skipping UserKnownHostsFile update
debug1: pledge: fork
Yes. I logged out from Plasma. Ctrl+Alt+F3 Login on console and deleted the folders.
I checked but there is no
authorized_keys
in my ~/.ssh/
This looks complicated. Depending on what your time allows, I’d suggest 1 of the following:
- (Re)move the
~/.sshdirectory and start everything from scratch; or - (re)move tthe files 1-by-1 from the
~/.ssh/directtory, trying after everey removed file, to see if you can find the culprit.
Since it appears to be VPS or something in that class - I assume you have a public/private key you use for the connection?
In that case you will not be able to connect just using the ssh command, unless you have configured your ~/.ssh/config with an entry.
Manually connection using a keyfile would look like
ssh -v -i ~/.ssh/<keyname>.key <hostname|op>
Removing content of ~/.ssh/ do the trick.
There was only 2 files:
known_hosts and config
Delete and restart. Everything is fine now.
Thank you all for the time!
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.