Ftp Error 12
Contents |
Material Urchin WebAnalytics Software is discontinued and is no longer supported. All Urchin documentation applies only to the Urchin product as it was at the time of discontinuation, and does not apply to any Google Analytics products or services. Error code list sftp error codes for failed FTP and HTTP remote webserver log transfers Overview sftp error code 255 An Urchin Log Source can be configured to collect a webserver log from a remote server via error -157: invalid reply from server ftp FTP or HTTP. Under normal circumstances, the transfer will be successful and no errors appear in the runtime log. However, if some error is encountered during
Err_ftp_failed
the transfer (e.g. an invalid username/password, remote server unreachable, remote log unreadable, etc.), Urchin will log an error code in the runtime output, as viewable in the Task History for the Profile. This error code appears in parenthesis next to the "failed" message after the webserver log transfer is attempted, e.g. (-9) The error ftp connection failed codes are listed below along with a text message explaining the problem that was encountered. Error Code List 1 Unsupported protocol. This build of curl has no support for this protocol. 2 Failed to initialize. 3 URL malformat. The syntax was not correct. 4 URL user malformatted. The user-part of the URL syntax was not correct. 5 Couldn't resolve proxy. The given proxy host could not be resolved. 6 Couldn't resolve host. The given remote host was not resolved. 7 Failed to connect to host. 8 FTP weird server reply. The server sent data curl couldn't parse. 9 FTP access denied. The server denied login. 10 FTP user/password incorrect. Either one or both were not accepted by the server. 11 FTP weird PASS reply. Curl couldn't parse the reply sent to the PASS request. 12 FTP weird USER reply. Curl couldn't parse the reply sent to the USER request. 13 FTP weird PASV reply, Curl couldn't parse the reply sent
are UTC Error trying to connect to an FTP server Moderator: Project members Post new topic Reply to topic Page https://forum.filezilla-project.org/viewtopic.php?t=34996 1 of 1 [ 8 posts ] Print view Previous topic | Next topic Author Message bluebogle1 Post subject: Error trying to connect to an FTP serverPostPosted: 2015-01-21 19:29 Offline 500 Command not understood Joined: 2015-01-21 19:26 Posts: 2 I'm a complete novice on this sort of thing, so please keep that in mind.Recently, I ftp error have been unable to connect to an FTP server I use regularly. The error message I get when trying is:GnuTLS error -12: A TLS fatal alert has been received.The log says:2015-01-21 11:28:55 9924 1 Status: Connecting to 64.183.44.190:21...2015-01-21 11:28:55 9924 1 Status: Connection established, waiting for welcome message...2015-01-21 11:28:55 9924 1 Response: 220 Gene6 FTP Server sftp error code v3.9.0 (Build 2) ready...2015-01-21 11:28:55 9924 1 Command: AUTH TLS2015-01-21 11:28:55 9924 1 Response: 234 AUTH command ok; starting SSL connection.2015-01-21 11:28:55 9924 1 Status: Initializing TLS...2015-01-21 11:28:55 9924 1 Error: GnuTLS error -12: A TLS fatal alert has been received.2015-01-21 11:28:55 9924 1 Error: Could not connect to server2015-01-21 11:28:55 9924 1 Status: Waiting to retry...2015-01-21 11:29:00 9924 1 Status: Connecting to 64.183.44.190:21...2015-01-21 11:29:00 9924 1 Status: Connection established, waiting for welcome message...2015-01-21 11:29:00 9924 1 Response: 220 Gene6 FTP Server v3.9.0 (Build 2) ready...2015-01-21 11:29:00 9924 1 Command: AUTH TLS2015-01-21 11:29:00 9924 1 Response: 234 AUTH command ok; starting SSL connection.2015-01-21 11:29:00 9924 1 Status: Initializing TLS...2015-01-21 11:29:00 9924 1 Error: GnuTLS error -12: A TLS fatal alert has been received.2015-01-21 11:29:00 9924 1 Error: Could not connect to serverFor what it's worth, I can still connect to other FTP servers, and other people are still able to connect to this one. Any help is much appreciated. Top Profile Reply with quote wolfberg