xml format of the protocoll file and its impact on the process

[openSuseman]

hello dear experts,

exported and imortet the credentials / settings from one to another machine... But the log to Server failed.

why.

could it have to do with the following circumstances:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

- well if i put all the well suited xml-info in to a notebook - and the document tree gets lost by this.

could this have any impact on the protocoll and the attempt to log to the server?

love to hear from you

[botg]

Where does this error message come from? It's nothing FileZilla ever says.

[openSuseman]

hello dear developer

we ve got this

Code: Select all

Antwort:	fzSftp started, protocol_version=8
Befehl:	open "vhost@www2.myserver.org" 625
Fehler:	Disconnected: No supported authentication methods available (server sent: publickey)
Fehler:	Herstellen der Verbindung zum Server fehlgeschlagen
Status:	Verbindung zum Server getrennt
Status:	Verbinde mit www2.myserver.org:625...
Antwort:	fzSftp started, protocol_version=8
Befehl:	open "vhost@www2.myserver.org" 625
Fehler:	Disconnected: No supported authentication methods available (server sent: publickey)
Fehler:	Herstellen der Verbindung zum Server fehlgeschlagen
Status:	Nächsten Versuch abwarten...
Status:	Verbinde mit www2.myserver.org:625...
Antwort:	fzSftp started, protocol_version=8
Befehl:	open "vhost@www2.myserver.org" 625
Fehler:	Disconnected: No supported authentication methods available (server sent: publickey)
Fehler:	Herstellen der Verbindung zum Server fehlgeschlagen

but the above mentioned sentense i have gotten while i have taken the xml-file (which was well-formated) and copy pasted it in my kate-window

suddenly the well formated xml dissapeardd and all lines were written in a single text-chunk.


well i am noi expert - does this have any impac on filezilla - and the capability of FileZilla to process the information of the file!?


love to hear from you

[botg]

The serve expect authentication through a public/private key pair. The new system does not have the private key the old system does. On the old system, is a key configured in the settings or is a key loaded in the system's SSH Agent?

[flagpole]

Where does this error message come from? It's nothing FileZilla ever says.

I've seen this message before...

I believe it was when I opened an XML file in a browser.

[boco]

FileZilla settings are not to be opened in a browser or browser-like environment. The message applies only to websites written in XML, because those usually have CSS information for formatting.

[openSuseman]

hello

well now i have the file in well formated xml
but i guess that i was not able to carry all the necessary information to the new computer

- it still does not connect.

btw. Is there more necessary than just t he so called configuration

is there also a pgp file needed - to conect to the server via SFTP?

[boco]

@botg did explain it already. Your SFTP server requires Public key authentication in addition to the password. The old system had the key saved, either in FileZilla or in the system's SSH agent. This type of key is not saved in filezilla.xml but elsewhere. While Windows uses the Registry for the SFTP keys, Linux surely uses some kind of flat file.

You need to salvage the key from the old system and transfer it to the new one, or, alternatively, re-obtain it from the server administrator.

[openSuseman]

hello dear buddy

many many thanks for the quick reply. This is convincing me. now i see it clear...

@botg did explain it already. Your SFTP server requires Public key authentication in addition to the password. The old system had the key saved, either in FileZilla or in the system's SSH agent. This type of key is not saved in filezilla.xml but elsewhere. While Windows uses the Registry for the SFTP keys, Linux surely uses some kind of flat file.
You need to salvage the key from the old system and transfer it to the new one, or, alternatively, re-obtain it from the server administrator.

i will do as acviced:


on a sidenote: i guess that this is exactly t he same issue - and circumstance i struggle with on the winSCP side of live - not i use winSCP sometimes..

see the thread https://winscp.net/forum/viewtopic.php? ... 060b361e8a

,,,,and after moving the config-files from one Notebook to another Notebook i have gotten an error_

system Error: error 2
Error code: 2 - Error message from server: No such file

Während des Protokollierens ist ein Fehler aufgetreten.
Das Protokollieren wurde abgeschaltet.
Kann Protokolldatei "c\users\myold-notebook\...nicht öffnen.
system Error: error 2

this is translated:

during the protocoll an error occurred: the protocol-process was interrupted and switched off
cannot open the Protocolfile "c\users\myold-notebook\...
the system cannot find the refered file.

well i guess that i have missed something. If i look at the paths in the winSCP - there lots of path are included
but - i guess that this would not help if i correct them all.

Code: Select all

  PuttyPath=
    LogFileName=
    ActionsLogFileName=
    [Configuration\History\PuttyPath] 0=
    [Configuration\Interface\Explorer] ToolbarsLayout=
    UserName=vhost
    PublicKeyFile=
    LocalDirectory=
    RemoteDirectory=/ 

i guess that a simple correction ofthe paths would not help...

in fact - i guess that i need to add the pgp-key file too. - it should be pretty the same as here in FileZilla


love to hear from you again

greetings

[boco]

OK, on the old Windows system:
1. Run Regedit.exe to open the Registry Editor.
2. Navigate to the following key at the left side:

Code: Select all

HKEY_CURRENT_USER\Software\SimonTatham\PuTTY\SshHostKeys

3. Here, all your keys are collected. If the new system is also Windows, simply export the complete key (by using the Export... item from the File menu).
4. You will get a file ending in .reg. Move this file to the new system and double-click it.
5. After confirming the import of the keys, they should work again.