gothamww
Forum Replies Created
-
yes, agreed, it’d be nice if there was another way.
Hi SpaceDroid – I changed my ssh settings to allow ftp to connect, then changed them back. I didn’t mind having my server exposed for a very short period of time.
Good lord. I had been getting those ftp prompts for years. And I just assumed that since SSH password authentication was off (the whole idea of giving out my sftp information seemed bad), that I couldn’t download plugins using the web interface, so I’ve been downloading them manually and installing them.
Turns out you are right – it was a permissions issue – not an issue with SFTP at all.
All fixed. Thank you for your help – and all other plugins are installing as well.
Thanks again!
Hi wfalaa, thanks for writing in. I’ve tried to connect in two ways:
the first way is simply typing the hostname into the hostname text box – I get:
Failed to connect to FTP Server hostname:21
so then I tried, adding the port on to the end of the hostname as in:
hostname:###
then I get:
Failed to connect to FTP Server hostname:###
I’m able to sftp from a client application using the same username and password. There are no IP address restrictions for that port on the firewall.
When you say there’s no need to download wordfence-waf.php… why is an sftp connection necessary? Something must be downloaded to my server – is there anyway to get whatever file is needed, or make the appropriate configuration change, without the wizard?
- This reply was modified 7 years, 10 months ago by gothamww.
Forum: Fixing WordPress
In reply to: Upgrade to PHP 5.2.9 causes apache segmentation faultThis was resolved finally.
The problem was that we still had an old rpm of mod_auth_mysql on our RedHat ES 3 server. Apparently this was causing some sort of conflict with php 5.2.9. I’m not entirely sure what the conflict is, but removing the rpm from our system resolved the problem and WordPress is now working.
-Charlie
Forum: Fixing WordPress
In reply to: upgrading to php 5.2.9 broke my login accessThis was resolved finally.
The problem was that we still had an old rpm of mod_auth_mysql on our RedHat ES 3 server. Apparently this was causing some sort of conflict with php 5.2.9. I’m not entirely sure what the conflict is, but removing the rpm from our system resolved the problem and WordPress is now working.
-Charlie
Forum: Fixing WordPress
In reply to: upgrading to php 5.2.9 broke my login accessSame issue for me – any progress?