Connect to FTP Through a SOCKS Proxy

See more FTP Examples

Demonstrates connecting through a SOCKS proxy using SocksVersion, SocksHostname, SocksPort, SocksUsername, and SocksPassword.

Background: SOCKS is a general-purpose TCP relay, so it carries FTP transparently. SocksVersion is the switch — 0 disables it, while 4 or 5 selects the protocol. SOCKS5 supports username/password authentication and is the usual choice; SOCKS4 supports only a user identifier. Because FTP opens separate data connections, a SOCKS proxy combined with passive mode is generally the most reliable arrangement.

Chilkat Go Downloads

Download Chilkat for Go

    success := false

    ftp := chilkat.NewFtp2()

    ftp.SetHostname("ftp.example.com")
    ftp.SetUsername("myFtpLogin")

    //  SocksVersion selects the proxy: 0 (default) = none, 4 = SOCKS4, 5 = SOCKS5.
    ftp.SetSocksVersion(5)
    ftp.SetSocksHostname("socks.example.com")
    ftp.SetSocksPort(1080)

    //  SOCKS5 supports username/password authentication; SOCKS4 uses only a user identifier.
    ftp.SetSocksUsername("myProxyLogin")
    ftp.SetSocksPassword("myProxyPassword")

    //  Normally you would not hard-code the password in source.  You should instead obtain it
    //  from an interactive prompt, environment variable, or a secrets vault.
    ftp.SetPassword("myPassword")

    success = ftp.Connect()
    if success == false {
        fmt.Println(ftp.LastErrorText())
        ftp.DisposeFtp2()
        return
    }

    fmt.Println("Connected through the SOCKS proxy.")

    success = ftp.Disconnect()
    if success == false {
        fmt.Println(ftp.LastErrorText())
        ftp.DisposeFtp2()
        return
    }


    ftp.DisposeFtp2()