• 16 Mar

    Azure Blob SFTP Public Key Authentication Failed

    Q: I am having some issues with getting SFTP private SSH keys to work. The same SFTP account works fine if I configure a password

    So far I have:
    Generated private key in Azure
    Used puttyGen on local system to generate keys and uploaded to Azure
    Tried both API vendor modes
    Tried different SFTP versions
    Enabled Stay Connected
    Switched to Keyboard-Interactive Last SSH auth order
    Enabled Control log

    It might be due to us using Azure Blob SFTP https://learn.microsoft.com/en-us/azure/storage/blobs/secure-file-transfer-protocol-support

    A: It can mean that our File Mover tried to use rsa-sha2-256 for the authentication, because the server indicated it supports rsa-sha2-256, but does not actually support it for the SFTP Public Key authentication.

    In version v2023.3.15.0 we added an extra option ‘Force User Authentication to Rsa-Sha1’ to achieve this. Important is to use our second API Vendor – CK.

    Force User Authentication to Rsa-sha1


    Update 30th of August 2023, in Limagito version v2023.8.30.0 there was another optimization regarding Azure SFTP server connection issues.

    SSH/SFTP: Fixed uncommon public-key authentication problems where the client and server are not agreeing on the choice of userauth key algorithm if RSA is used and the server supports the rsa-sha2-256 and rsa-sha2-512 host key algorithms.


    #FileTransfer #Azure

    If you need any info about this ‘Azure Blob SFTP Public Key’ issue, please let us know.

    Best regards,

    Limagito Team

  • 06 Jun

    SFTP Connection errors 10054 (0x2746)

    Q: SFTP Connection errors 10054 (0x2746). Is there something we can look at in regards to this error?  What causes it and if we can resolve? We’ve encountered a situation twice now where a vast amount of rules appear to stop processing to 1 particular server.  The rules in web remote all turn green and stay green as if they are currently being triggered, but there is no output on the runtime log and no transfers take place. To resolve the issue we’ve restarted the Limagito server, and rule processing occurs normally again. Are we able to provide you with some logs that might help shed light on what’s occurred?

    We have 173 rules, and of the failures they seem to be with this 1 SFTP server, destination and source rules. Is there a preference in which one we use? We scan the rules every 70 seconds.

    • With our SFTP Source Code Vendor 1 (SB) the error message looks like:

    6/3/2022 9:12:57 AM SFTP Connected Error

    6/3/2022 9:12:57 AM Connect attempt 1 Exception: Connection lost due to error 10054

    6/3/2022 9:12:57 AM Connecting SFTP Server..

    6/3/2022 9:12:57 AM Cyclus [SFTPGET]

    6/3/2022 9:12:57 AM Start Source Thread

    • With our SFTP Source Code Vendor 2 (CK) the error message looks like:

    SFTP Connection Errors

    A: With 70 seconds scan time we would certainly enable the ‘Stay connected’ option (Common Tab of SFTP setup). We guess this SFTP server is no longer accepting new connections (after x time). Please also check the ‘Hint’ in the feedback when using our SFTP Source Code Vendor 2 (CK). If you trigger the rules often then some SFTP servers will find this (connects/disconnects) suspicious and will no longer allow new connections for a certain time.

    • SFTP Setup (Source or Destination), enable ‘Stay Connected’.

    SFTP Stay Connected option

    #SFTP #Filetransfer #Filemanagement

    If you need any info about this ‘ SFTP Connection errors’ question, please let us know.

    Best regards,

    Limagito Team

    By Limagito-Team Error SFTP
  • 17 Apr

    Use referenced files during FTP and SFTP upload with shortcut files

    Use referenced files during FTP and SFTP upload with shortcut files

    Q: After hearing many positive testimonials regarding your product, I finally have the opportunity to work with it. I’ve been tinkering for a few weeks and I’m very impressed with the functionality and speed. I am attempting to architect a rather challenging solution. If possible I would like to present an overview of the requirements and the approach I have been building out and testing. Obviously, I am open to any suggestions regarding a better approach to accomplish these goals with your product.

    I need to deliver approximately 9,000 files daily to each of (8) FTP destinations. That’s not an actual 72,000 files daily as each of those eight destinations utilize a text file filter. I know from experience with our current solution that this isn’t as easily achieved as one would think. At peak times we will have more that 2,400 files flowing in per hour. With that in mind I’m trying to design in as many efficiencies as possible.

    These files average 4MB. In order to minimize storage and file duplication times, I wanted to create a shortcut alias to the original file. When that file is found in an input, I can use the reference to the original file. I can’t see where this approach would be possible in your product.

    I did discover the create Shortcut function in the WIN as Destination and started pursuing that. When files flow into input, I move the original to a ‘processed’ dir and create an alias. Another process monitors the alias dir and copies/seeds all aliases into each of the (8) sub-folders using your ‘Output files to all subdirectories’ option.

    Each of these (8) inputs for FTP destinations are using text file filters such as %FCA setup in Rule parameters. Some of these filters are 1,200 lines. I wasn’t sure how well this would work, but testing and speed far exceeded any expectations I had. I am also using a text file for calculating the destination dirs. This involves several pascal scripts as described in a solution I found in your blog. This is all working perfect.

    The biggest issue I currently have and possible deal breaker is that the destination file is the shortcut alias. Obviously I was hoping to get the original in the destination.

    Sorry for the verbose email. Any assistance or guidance is greatly appreciated.

    A: We added a new option in version v2022.4.17.0 to achieve this.

    Feedback customer:

    This is incredible news! I never would have imagined we could get responsive support like this. I demonstrated my solution utilizing your product this past Friday. Everyone was impressed and couldn’t identify a single area that needed improvement.

    Huge thanks to you and your team.


    When this option is enabled and a shortcut (.lnk) file is found in the Source then the referenced file will be used during the FTP (or SFTP) upload.

    Limagito File Mover handle shortcut files

    RunTime Log: information about the referenced file is available in the log. The referenced file is used during the FTP upload.

    Limagito File Mover upload shortcut files

    #Filetransfer #SFTP

    If you need any info about this ‘shortcut files’ option, please let us know.

    Best regards,

    Limagito Team


    FYI, in the ‘WIN as Destination’ setup you have an option to create Shortcut files.

    Limagito File Mover create shortcut files


    By Limagito-Team FTP SFTP , ,
1 2 3 4 5 6 11