Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter carlfink

    (@carlfink)

    OK, Clayton, your advice about installing PHP support for SSH actually got me past the FTP thing. Thanks. (Note to future readers of this thread: you should also restart Apache, or at least I had to before WordPress recognized the SSH support.)

    Still can’t upgrade, mind you. The new inscrutable error message is:

    “Unable to locate WordPress Root directory.

    Installation Failed”

    (Also incorrect usage, of course.)

    Thanks for explaining, Jan. As I may have angrily implied before, my objection is not to the functionality, it’s to the pointlessly opaque error message. Why couldn’t what you write be included in the WordPress administration screen that otherwise will confuse, I must presume, more people than just me?

    Note that this new error message is also utterly useless and in fact nonsensical. Obviously WordPress can locate the root because WordPress is running! There must be some other actual problem, presumably another permissions issue, but I can’t tell. Apache is running as www-user and www-user has full access to the WP directory, so I don’t get it.

    Note to Clayton: I didn’t actually set up this server. I haven’t done much Linux administration for the past several years, so I paid my ISP to set this one up for me. If there’s a documentable flaw, I would like to point it out to them so they can fix their procedures.

    Almost instantaneous edit: actual server logs and also turning on WordPress logging showed nothing useful.

    Thread Starter carlfink

    (@carlfink)

    Clayton,

    WordPress is perfectly capable of telling me more than “No.” For instance “Connection refused” or “Invalid ID/password pair.”

    Typo above, I installed ftpd-ssl. On Debian, like I wrote. Debian jessie, to be exact. Never occurred to me that a package named “ftpd-” anything would need a separate ftpd to go with it–my whole point here is NOT TO INSTALL FTP, which I don’t want or need and which is a gigantic security hole.

    I’m actually irritated enough to look at WordPress alternatives, and I have liked and used the product for years. This is so completely unnecessary.

    Thread Starter carlfink

    (@carlfink)

    Thanks, jonradio, but I just logged in and changed the ownership to www-data (which Apache runs under), permissions -rw-r–r– (which should let www-data write to the files and directories) and still am restricted to FTP or FTP with SSL. Note that Clayton to the contrary, this is not SFTP, which works fine, but “FTPS (SSL)”. I’ve installed the ftp-ssl Debian package but WordPress still unhelpfully says, “ERROR: There was an error connecting to the server, Please verify the settings are correct.”

    I actually used to write error messages at my last job. I’d be humiliated if it was known I was responsible for this one, which is synonymous with, “That did not work. Do something different.” It’s as unhelpful as it is possible to be and still be a grammatically-correct sentence.

    Setting WP_DEBUG to true has zero effect–no error is logged.

Viewing 3 replies - 1 through 3 (of 3 total)