These instructions apply to users who are receiving their statements via sFTP. If you elected to receive your statements that way, you would first need to generate an RSA Key pair. If you need guidance to set up the Key pair, please refer to this article, which is a prerequisite to the instructions below.
1. Start WinSCP.
2. Click on Session and select New Session.
3. If you see an existing Interactive Brokers sFTP site in the list, select it and jump directly to point 5. If you do not have such site configured yet, enter:
- xfer.interactivebrokers.com in the Host name field.
- 32 in the Port number field.
- The username provided to you by Interactive Brokers in the User name field.
Select SFTP as File protocol:
4. To ensure the session is using the appropriate Private Key file, Click Advanced > Authentication. Verify that the Private Key file field has the appropriate Key file selected. Click OK.
5. Click Login to connect with the sFTP host and retrieve reports in clear text.
6. Drag documents from the right side panel (sFTP host site) to the left side panel (local machine host).
Common issues and solutions
A. The Login Credentials Provided are Incorrect
-
Ensure the correct login details are being used to connect to the sFTP server. The username and password you are entering should match the ones you have received from the Reporting Integration Team.
-
Confirm you have configured your sFTP Client to use the Private Key file for the logon authentication (see step 4. of the above procedure.)
B. Server Refused Our Key
-
Try accessing the sFTP server using a different Client (FileZilla, WinSCP, CyberDuck, ect.)
-
Ensure the Private Key file being used to Authenticate the server login attempt is related to the Public Key you originally sent to the Reporting Integration Team.
-
Should the above checks be unable to resolve the issue, please generate a new RSA Public/Private Key pair and send only the Public part to the
Reporting Integration Team, as per
IBKB3842.
C. Connection Timed Out
-
In case you have an antivirus or a security software installed on your machine, make sure it is not blocking the FTP connection attempt. Normally, security software allows to set up exceptions for specific connections in order to whitelist them.
-
Verify that the public IP Address of the machine running the sFTP client, is the same you have originally provided to the Reporting Integration Team for being whitelisted. You can discover your public IP Address by searching the Internet for “
what is my IP”. If your current IP Address is not the same you provided to us, please send it to our
Reporting Integration Team for being whitelisted.
-
Ask your network administrator/s to confirm that your firewall allows both incoming and outgoing traffic from/to xfer.interactivebrokers.com on port TCP 32.
-
Should the above steps be unable to resolve the issue, please generate a new RSA Public/Private Key pair and send only the new Public part to our
Reporting Integration Team, as per
IBKB3842.
Related articles
KB3842 - Using GPG/RSA encryption keys to guarantee the privacy and security of your Reports
KB3968 - Generate a key pair using GPG for Windows
KB4205 - Generate a key pair using GPG Suite on macOS
KB4108 - Decrypt your Reports using GPG for Windows
KB4210 - Decrypting Reports using your PGP Key pair on macOS
KB4407 - Generate RSA Key Pair on Windows
KB4819 - How to set up sFTP for using Certificate Authentication on Linux
KB4578 - How to Access your Reports using FTP on Windows
KB4580 - How to Access your Reports using FTP on MacOS
KB4410 - How to set up sFTP for using Certificate Authentication on macOS
KB4411 - How to backup your public/private Key pair
KB4323 - How to transfer your public/private key pair from one computer to another