removed your email. If you’re subscribed for updates, you’ll get ’em. Oh look! You are 🙂
What’s wrong with allowing *.wordpress.org?
My system administrator at the university don’t want to allow *.wordpress.org via WordPress’s FTPS (SSL).
They are putting on a restriction scheduling and asking my team to check what is the IP range when this updates requests is made from wordpress.org.
Hope this explains.
Thanks
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.
I believe you may be mixing up two different problems. That question is (usually) for your web server to upload updates to yourself (your blog).
The updates are retrieved via http not ftp; it’s displaying that message because your WordPress installation could not write to it’s own filesystem.
(And when Ipstenu comes online again, I hope she’ll correct me where I’m off a bit 🙂 )
Can you adjust the file system ownership and permission on your blog’s file system? Or if that’s not an option, how does your SA feel about using ssh/scp/sftp instead of ftp to access the web server?
The updates are retrieved via http not ftp; it’s displaying that message because your WordPress installation could not write to it’s own filesystem.
I actually don’t know 😉 I think it’s FTP via PHP, though, which is why you have to put in your FTP info and say if you have FTP or FTP(SSL).
Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
I really need to look that up…
I’m almost Ivory Soap sure it’s libcurl and http GETs to retrieve the updates. But when WordPress needs to write the files to your installation, if it can’t (unsuccessful) it prompts for you for your FTP credentials and tries to use FTP to save the files.
Nacin would know for sure 🙂
We’ll bug him when he’s done teaching his cousins programing for the holidays 😉
Thank for the update guys.
Yes, for most of my other projects. I will enable the FTP or FTP (SSL) as you guys recommend.
This is because I am deploying into a university’s network with a Standard Operating Environment (SOE). You know those big boys like to in place the IT Governance.
Unfortunately, FTP is one that the security committee strictly disallow for system administrator and my team to enable. We have speak to them, they just don’t buy it due to security reasons.
But, they updated if we know where or what the IP range it. They will get the security programmer to set it based on time scheduling.
Sorry to bother everyone on these holidays.
In the meantime, you can manually update WP, you know.
ETA – 72.233.56.253 is one of the IPs.
Thank, yup that is what we have been doing past 2 years.
thanks.