We are moving towards a simpler process with authentication for FTP. Currently we use different authentication passwords for different FTP services, and we want to make management easier for authors by having one set of credentials for FTP.
We plan to make changes to ftp.marketplace.envato.com on the 15th May, 2019 at 10am AEST. During this change the FTP service will be down for one hour, and after this the passwords (API keys) that are currently used for ftp.marketplace.envato.com will become invalid.
So what do you need to do?
This change will affect any authors that upload via ftp.marketplace.envato.com. If you currently use ftp.author.envato.com to upload, then you won’t need to do anything differently.
If you’re an affected author, after the 15th May you will need to change the way you currently generate your FTP password (API key).
Yes, currently video authors for stock/motion graphics use a different uploader and a different FTP server. Most authors will use the ftp.marketplace.envato.com and so any author using this FTP will need to create new credentials.
Currently only authors that upload certain media types (video) use the ftp.author.envato.com FTP server. These are usually really large files and require special post processing (watermarking, previewing, thumbnails) and are handled in a different system. The majority of authors will be using ftp.marketplace.envato.com. In this case we are migrating the authentication to be the same for both groups of authors.
Simply on the 15th your current password that you use for ftp.marketplace.envato.com will no longer work. You will need to create a new password (API key). We will be updating the docs to reflect this on the day. Stay tuned to this forum for links on the day.
No, you can keep your existing one. It is a very good idea to generate another new API token with only the required privileges for FTP authentication (which we will show in the documentation once it is updated). You can have several API tokens.
Hi folks, I’ve just tested out the FTP server and was able to authenticate successfully. @NeuronFX, @CleverSoft: are you still experiencing problems? If so, can you provide further detail (error messages, screenshots, etc.)?
Feel free to raise a support ticket if you’d prefer.