I'm planning to give this extension a try later, but I have gotten that 530 before. If your FTP is hosted on a IIS Server, this documentation may help resolve your issue. If not, it may point you in the right direction. That 530 can be a pain to get rid of sometimes...

I'm planning to give this extension a try later, but I have gotten that 530 before. If your FTP is hosted on a IIS Server, this documentation may help resolve your issue. If not, it may point you in the right direction. That 530 can be a pain to get rid of sometimes...

I gave this a try and I'm getting The remote server returned an error: (530) Not logged in as well. Has anyone figured out what the problem is? The above resolved this issue for me before, but not this time.

The extension uses (on different places) EncodeURL() for the username and Password... This doesn't work if one has a special character.......Without EncodeURL it works fine.....

Thanks Jeroen. I confirm that removing the EncodeURL from the Username and Password fields allows me to log in without getting the 530 error.

If anyone else is having this issue and wants to test it with the included OSFtpWebReq module, you need to go into each screen action of the HomePage and look for the Assign step called "Set FTPServerData". There you'll see the EndodeURL functions used for the Username and Password fields. Remove this function and publish the module to try again.

Hi, I just tried but can not connect to remote server, think is because the network administrator does not allow the access from that page. He included the ip addresses provided by OS and first we were getting that connection error but now is the 530 not logged in error