The BitKinex FTP client can only be configured for an HTTP or SOCKS type proxy. It does not know how to use an FTP proxy. This document will configure the BitKinex FTP client to use FTP over HTTP and not SOCKS. Assuming the HTTP proxy is configured on port 8080, you will see a CONNECT ip.address.of.ftpserver:21 to port 8080 on the wire between the workstation and the proxy. This is normal and expected. The data provided below was gathered using the BitKinex v3.1.1 FTP client against a proxy running SGOS 220.127.116.11. SGOS 18.104.22.168 was also tested.
NOTE: Once the proxy settings are all configured on the client, if the BitKinex FTP client works once and then fails several times and then works once and then fails, please see 000014404 for a way to work around the issue.
CONFIGURING BITKINEX TO USE THE PROXY
- Open or launch the BitKinex FTP client.
- Click on File > Options > Firewall/Proxy. In the Firewall/Proxy settings, configure the following:
- Type: Select HTTP from the drop down box.
- Server: Enter the DNS name or IP address of the ProxySG.
- Port: Enter the HTTP port configured on the ProxySG to intercept HTTP traffic. For explicit deployments, generally this is port 8080.
- User: Enter the proxy user's name. In this instance, the proxy user is bob.kent .
- Password: This is the proxy user's password.
- Click on the OK button to save and close your changes.
- Test. In your list of FTP sites, select the site you want to connect to and then connect. The FTP client will make a CONNECT request to the HTTP proxy and it will send over the user's credentials that were stored in the firewall/proxy settings page. OBSERVED BEHAVIOR: In SGOS 22.214.171.124, the directory listing seemed to take a while for it to come up. So wait a while (30 - 60 seconds) for the directory listing to appear.
Below is a screen shot of the BitKinex Firewall/Proxy settings page.