More on how to find your domain root: http://unifysupport.unitinteractive.com/entries/174654-how-do-i-fin...

If you are trying to save your FTP info and get no response, you may not have FTP enabled for PHP on your server. It is rare that this could happen, but you do want to make sure that it is enabled. It helps work around many permissions issues that servers could have.

Do you support accessing the server with SFTP in addition to FTP?

I have the same question as Sean. My host allows SFTP but not regular FTP will this work?

Thanks for the questions Sean and Jeff!

Unfortunately, no. At this time, Unify does not work with SFTP. We are working on integrating it in the future. In the meantime, Unify does not require FTP to work... with most server setups, you can publish changes without saving your FTP info. FTP functionality has been added to get around any permissions issues that could come up.

Please let us know if you have any further questions. Thanks!

----------------------------------------
Nathan Ford
Lead Developer on Unify
Unit Interactive

Lack of FTP support isn't completely uncommon. I have one client on Pair Networks and they don't have FTP enabled. 

I am getting "Error: There is an error in your FTP credentials. Please try entering them again." whenever I save my FTP credentials; I have tested these with a basic PHP connection file which works fine; any idea what could the problem be?

The server is a Windows 2003 server; could potentially be a permissions issue? Where does Unify save the FTP details?

The FTP server is also locked down by IP so that this user can only connect from my machien or the server itself; is Unify using any kind of external machine to verify the details?

Other than that I can't really see what's wrong! Is there anyway of getting a more detailed error message?

Hey Rob.

Are you sure the domain path is set correctly? If so, please create a ticket (by clicking “report bug”) so we can get more details to help you out here. Thanks for letting us know.

----------------------------------------
Nathan Ford
Lead Developer on Unify
Unit Interactive

Hi Nathan, thanks for the response! It turns out to have been a couple of things - a couple of them was me being an idiot :o) I'll detail them here in case they help anyone spot their obvious mistakes:

I had set up Unify as a virtual directory in IIS for the web application, however not in the FTP server, meaning that as far as the FTP server was concerned, the unify folder did not exist, so it couldn't save anything.

Secondly, and more stupidly, my IP settings were not inherited, so it wasn't allowing the relevant IP to connect anyway.

The third thing I could only get working with a change to Unify; after checking my FTP logs against the Unify connections vs working Filezilla ones, the only difference I found was that Filezilla was creating the file with a leading /, whereas Unify was not, although I did include a leading slash in the domain root.

To get it working quickly, I changed line 48 in functions/ftpcreate.php to:

$remotefile = ($ftpwd[0] != "/" ? "/" : "").$ftpwd.$path.'ftpvars.php';

...but I don't really want to be running a modified install, especially one with what seems to be a server specific hack in :o/

How come the leading / is being stripped?

Do you still want me to create a ticket for it?

We have fixed this issue with the leading "/" in versions after 1.3.7.

We have found that for some server setups, you may want to use "localhost" as your server name, rather than your domain. Also, removing "ftp." at the beginning of you server can also fix connection issues.

When will " versions after 1.3.7." be released?  Is there a version greater than 1.3.7 currently available?

Hey Kerri.

1.3.8 is not yet available, but we hope to have it out as soon as we can. Until then, you can use the attached file as a patch. Just replace unify/functions/ftpconnect.php with the attached file.

Please let us know if you continue having FTP issues. Thanks!

----------------------------------------
Nathan Ford
Lead Developer on Unify
Unit Interactive

Hello.

I've tried the fixes on this page (except editing ftpcreate.php -- don't really want to do that yet), and I've had no luck with ftp credentials.

Using vsftp, and a chroot, so that once logged in, user is in the html directory, and owner of all files therein.  Permissions should not be an issue.

username/password combo work perfectly with ftp client.

For server, I've tried the FQD, and I've tried localhost.

For domain root setting, I have tried a period, and a forward-slash, and, even though vsftp shouldn't want/need it, I've tried full system path.

I tried replacing ftpconnect.php with the version on this page.

Failed attemps log as follows in the httpd error log:

[Fri Nov 12 12:49:34 2010] [error] [client 173.13.176.75] PHP Warning:  ftp_fput() [<a href='function.ftp-fput'>function.ftp-fput</a>]: Could not create file. in /var/www/html/unify/functions/ftpcreate.php on line 50, referer: http://www.gyroscopeinc.com/unify/settings/ftpinfo.php
[Fri Nov 12 12:49:39 2010] [error] [client 173.13.176.75] PHP Warning:  ftp_fput() [<a href='function.ftp-fput'>function.ftp-fput</a>]: Could not create file. in /var/www/html/unify/functions/ftpcreate.php on line 50, referer: http://www.gyroscopeinc.com/unify/settings/ftpinfo.php

I'm not sure what I'm missing.  Any advice?

TIA,

Eric Thompson

Hi Eric, just to say, my ftpcreate.php hack above is fixed by both the ftpconnect.php fix in this thread and the latest version of Unify, so there is no point trying it anyway. 

A silly other problem I had was that my FTP server had an IP whitelist, which did not include its own IP. 

Do you have access to your FTP server logs? That'd tell you what file it is actually trying to create.

Rob,

Thanks for the input.

The ftp log alludes only to one file, the following:

//unify/functions/ftpvars.php

Not sure why the double forward slash . . .

That file is mod 644, and the user in question is the owner of that file. 

hmmm.  My various attempts using different paths result in some strange paths; e.g., some start with

/./unify/functions/ftpvars.php

One that looks correct (but still did not work) was

/var/www/html/unify/functions/ftpvars.php

The ftp server I'm using is vsftp, and I'm using it's chroot feature, which is important for the server in question.  I hope that is not causing the problem.  As for ip's allowed to connect, any and all are allowed; i.e., there is no whitelist or blacklist.

Eric

Hi Eric, I last used a Unix system in 1996, so I'm not sure how much help I can be :o)

However, if the chroot feature does what it sounds like, then I would say that /var/www/html/unify/functions/ftpvars.php is incorrect; it may be the filesystem path, but presumably the path as far as the FTP server is concerned would be different? I would expect it to be /unify/functions/ftpvars.php, or possibly /html/unify/functions/ftpvars.php depending on what the FTP server considers the root once the user is logged in.

I had problems like that because of the odd way MSFTP does stuuf, and was helped by the fact that FileZilla shows me the what the server considers the full path as soon as a successful login occurs; if your client shows that, then you can hopefully mess around with the domain root until the two match?

I have two websites hosted on go daddy using unify.  I used the same settings in my FTP client, and I can upload files fine, but they settings will not save in unify.  Any ideas?

As of version 1.3.16, there were many updates for the FTP info and publishing. Please update if you haven't already!

Any chance you will support FTP with TLS encryption (FTPeS)?

Yes, we are working on improving Unify's security in an upcoming release. Thanks for the question!