That’s ok.expected Fire does not make a live connection to the server itself (like Water does), but the debugger should still be able to connect as needed (which it tries to do, but fails with the error message form your second screenshot:
This looks like you have neither a password nor a key file specified for the server. What does your CrossBox.xml file look like (X out the password before posting, if you have one in there), and do you have an ~/.ssh.id_rsa key file on your client system?
odd. and when you check show password, is the password correct?
if so, this should work, I guess is;'ll have to debug this on Monday. by first finding a server that uses passwords l;). as workaround, can you try to use keys? much securer, anyways…
Im using a private point to point VPN, for that reason the security is more relaxed. Have no idea how to use keys. If you can give me directions I can try.
ive had this too. not seems that some SSH implementations dont like “-----BEGIN OPENSSH PRIVATE KEY-----” keys, only “-----BEGIN RSA PRIVATE KEY-----”. It depends omg the system where you generate they key, apparently. Check your key file; I’m not sure if simply changing there string from OPENSSH to RSA suffices, or if its actually a different format…
Turns out, recent openssh changed the fileformat for this. If you pass -m PEM on the command line (of ssh keygen) it will create a compatible key format.