Robo-FTP Server

Frequently Asked Questions

The FAQ list is a great starting point for basic questions about what you can do with Robo-FTP.

Orange_arrowOrange_arrow Browse the FAQ list now

Getting Started

Browse these tutorials and sample scripts to get up and running with Robo-FTP in minutes.

Orange_arrowOrange_arrow Browse tutorials and samples now

Contact Technical Support

If you can't find the answers you need online, get in touch with our Technical Support staff.

Orange_arrowOrange_arrow Contact Technical Support now

Professional Services

Need more than basic technical support? Our Professional Services team can help you deploy a complete solution.

Orange_arrowOrange_arrow Contact Professional Services now

Enter search queries below or use the tag links to the right to browse the knowledge base by category (Show All Tags).

Robo-FTP is unable to send or receive files when connected to an HTTP or HTTPS server


I can connect to a web server but not transfer files.

Possible cause

You may not have permission to transfer the file.


Enable the Trace Log and retry the transfer. This will not fix the problem but it will record important diagnostic information in the Trace Log.

The Trace Log shows all the requests sent to the server by Robo-FTP and all the responses sent back by the server. If the server's response is 401 Authorization Required then you may be able to resolve the problem by modifying your script to add the /httpauth=auto option to the FTPLOGON command line. If the server's response is 403 Forbidden then that means the server rejected your authorization credentials.

Article last updated: 2017-08-03

Tags: Robo-FTP, HTTP, HTTPS, 401, 403

Home | Solutions | Professional Services | Technical Support | Download | Company | Contact Us | Partners | Site Map | Terms of Service | Privacy Policy | Buy Now