The FTP platform will allow you to log into your site using FTP protocol.

SFTP \ FTPS connections require that customers register all public IP addresses that connect to the Thru platform via these protocols. To register an IP address the customer must provide the public IP address of the client connecting to the Thru platform via one of the secure FTP connections. If you don’t know the IP address, you can point a browser to https://whatismyipaddress.com/ and the IP address will be displayed. Next, send an email to helpcenter@thruinc.com to request the IP address(es) be whitelisted for FTP connectivity.

To allow anonymous FTP access to the Thru Platform:

  1. Check Allow anonymous access to this site. It is disabled by default. Even when this option is disabled, users can access the portal via FTP and FTPeS using FTP clients when configured with user credentials.

You can also specify how long a session will stay active (in minutes). If you want the session to never expire, input the time as 0 minutes.

  1. Click Save.

Setting Up Anonymous FTP Access

  1. Create a regular Thru user named anonymous. You can decide if you want to create a home folder and/or share other folders for anonymous access.
  2. Activate the user by following the activation email and set a password. This password will be required for web access but not for FTP access.
  3. Set read/write permission to the folders you would like to expose for anonymous access.

Client FTP Configuration Information

To configure your FTP client to Thru, refer to the following information:

  • Host: Depending on which global region is being used, one of the following will be entered.

SJC-FTP.thruinc.net – Chicago (50.56.9.35) (same as ORD1 but supported for backward compatibility)
ORD1-FTP.thruinc.net – Chicago (50.56.9.35)
HKG-FTP.thruinc.net – Hong Kong (119.9.69.115)
LHR-FTP.thruinc.net – London (212.100.245.147)
Trial-FTP.thruinc.net – For Demo and Trial sites in Europe (212.100.245.157)
SYD-FTP.thruinc.net – Sydney (119.9.2.36)

  • Protocol: FTP
  • Encryption: Require explicit FTP over TLS
  • Logon Type: Normal
  • User: The user is a combination of portal name\user name; Example: demo.thruinc.net/name@company.com
  • Password: The password is the same one used for Thru portal authentication.

Egress connections to Thru FTP services may need to be enabled on a corporate firewall. If the error “The server rejected SFTP connection, but it listens for FTP connections” appears after attempting the authenticated connection, it is most likely that the Thru FTP host has to be added to the firewall whitelist.

Feedback

Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Please do not use this for support questions.
For customer support, please contact us here.

Post Comment