Failed to connect to FTP Server WordPress 2.7 – Auto Update

Posted on December 16, 2008
Filed Under The WorldWideWeb | 19 Comments

I seem not to be able to find the issue with a little annoying bug?

I fight with in the new WordPress 2.7 automated update for plugin setting panel.

Although I’m 100% positive the ftp info is right, I get the error message saying it failed to connect. Double checked with my usual ftp client works like a charm. Did some research and found this thread not much help so….

Anybody had the same issue and found the cure? Please do let me know.

  • Wordpress facing downtime
  • How to get rid of choppy video streaming playback from Network attached storage (NAS / VLC / Mac OS X)
  • WP Canonical URLs – the server is redirecting the request in a way that will never complete
  • Why did WordPress remove the incoming links monitoring?

    • Comments

    19 Responses to “Failed to connect to FTP Server WordPress 2.7 – Auto Update”

    1. JohannesNo Gravatar on December 16th, 2008 10:36 am

      Does your webserver/firewall allow outgoing connections?

    2. Frank FuchsNo Gravatar on December 16th, 2008 12:05 pm

      Good point – not really sure about this will need to check.

    3. ebtaNo Gravatar on December 18th, 2008 11:03 pm

      Yes, I have the same problem with you. Does anybody has found the answer ?

    4. stephenNo Gravatar on December 23rd, 2008 12:40 am

      I have uploaded wp 2.7 on two different servers, a Linux and a Mac, fine with the first, uploading problems with the second. Con only deduce that thacould be the problem

    5. MeNo Gravatar on January 16th, 2009 7:45 pm

      Try writing only the name of your domain (for example “locallytype.com”). Wordpress is supposed to automatically locate the installation paths. Works for me, and I’m using Plesk. But I have another problem with PCLZIP which I just can’t solve :-(

    6. suzNo Gravatar on February 2nd, 2009 1:23 am

      I am having the same problem

    7. KuraattoriNo Gravatar on February 11th, 2009 12:13 am

      I had the same problem, many many times. One of my blogs on the same server had none of these issues, so I wondered if it really has anything to do with any ftp-credentials or server settings. I checked the group and file owners, and found out that even the parent directory of my blog had an effect on automatic upgrade. Immediately after I chgrp’d my blog’s parent directory so that apache could write to that too, all the problems went away. Could be just a fluke in my case since I really don’t understand why that would matter, but since this is really annoying problem, I thought this _could_ be of some help to someone.

    8. JohnNo Gravatar on February 14th, 2009 1:51 am

      Hey guys… this has been bothering me since I upgraded to 2.7.

      I just got it working by using the “reset file permissions” option in the back-end of my hosting service… network solutions. I blogged about it here…
      http://blog.unseenbattle.net/wordpress-27-plugin-auto-install-not-working/

      I hope this helps someone.

    9. KevinNo Gravatar on March 3rd, 2009 4:55 am

      This is a solution that often works with Plesk install of wordpress for updating from within WP.

      Hostname: try using localhost or localhost:21
      User: Your normal FTP Username
      Pass: Your normal FTP Pass.

      If successful, your screen will go blank for a little while during the upgrade and then you will be fine.

      Good luck!

    10. Sherman CoxNo Gravatar on March 7th, 2009 3:01 pm

      That localhost thing worked for me…Thanks…it was workign and just stopped working…

    11. PersonNo Gravatar on March 11th, 2009 6:22 am

      It’s bug in the WordPress code, although I suspect they’re not ready to admit it yet. They check not to see if the update can correctly install the files, they check to see if the owner of a test file created is the same as the directory owner.

      So they’re failing out on updates that by all rights are working correctly.

    12. Antonis on April 1st, 2009 9:36 am

      Thanx Kevin! localhost:21 worked for me too!

    13. MjNo Gravatar on May 16th, 2009 10:10 am

      I have read in wordpress forum that localhost worked for them. But in my case its localhost:21

      Thanks!

    14. rahulNo Gravatar on September 14th, 2009 6:59 pm

      @kevin
      thnx……..it worked

    15. AndrrewNo Gravatar on October 26th, 2009 6:47 pm

      Stephen, Did you manage to get it working on the Mac? as I have the same issue using Wp on my hard drive for testing.

      Cheers,

    16. macsolversNo Gravatar on February 5th, 2010 6:12 pm

      Entering localhost or localhost:21 in the Connection Information screen didn’t work for me. I’m running WP 2.9. I checked permissions for the WordPress folder and it’s set as 755. I changed it to 775 and obtained the same feedback (Username/Password incorrect for …). I replaced wp-config.php with a fresh copy and still get the same password error. Thoughts?

    17. JMNo Gravatar on March 13th, 2010 2:28 pm

      The localhost solution just worked for me – many thanks!

    18. Mohit SharmaNo Gravatar on April 13th, 2010 2:57 pm

      Kevin thanks works :-)

    19. ErwinNo Gravatar on July 20th, 2010 9:30 pm

      The localhost work for me!!! ty

    Leave a Reply