when uploading an image to media so The uploaded file could not be moved to wp-content/uploads error show, I have to give 755 uploads folder permission and nobody, but the error is same. I have used Linux server.
![]()
The uploaded file could not be moved to wp-content/uploads. Fareed - Wed, 2014/05/28 - 13:23 I have windows hosting and I have congfgured wordpress with FileZilla.
This article explains and resolves the issue very well:The basic premise is that the identity of the process running your httpd / apache / web server thread must have write access to your upload directory.To resolve the issue:.Check which account your webserver is running underUpdate: On Unix use.ps aux egrep '(apache httpd)'. This will show a list of processes for the web server along with the identity of the process under which its running e.g.' Nobody'nobody 8718 0.1 0.4 130? Sl 17:11 0:06 /usr/local/apache/bin/httpd -k start -DSSL.Update the permission of the upload directory to allow that account to write to it.Update: On Unix, you can use.chown -R nobody //wp-content/upload/You can also amend permissions for this account (at the rquired location) to ensure it has write permissions using chmod or filezilla and cascade the changes to the directories as necessary.Check out the linked article for a detailed breakdown. Hope that helps!:). I have searched and found that the problem is from server provider.Typically, all files should be owned by your user (ftp) account on your web server, and should be writable by that account.
On shared hosts, files should never be owned by the webserver process itself (sometimes this is www, or apache, or nobody user).Any file that needs write access from WordPress should be owned or group-owned by the user account used by the WordPress (which may be different than the server account). For example, you may have a user account that lets you FTP files back and forth to your server, but your server itself may run using a separate user, in a separate usergroup, such as dhapache or nobody. If WordPress is running as the FTP account, that account needs to have write access, i.e., be the owner of the files, or belong to a group that has write access.
In the latter case, that would mean permissions are set more permissively than default (for example, 775 rather than 755 for folders, and 664 instead of 644). I got this error on a cPanel hosting account, where the disk quota (for the account) was not an issue. After delving into it for a while, I found that cPanel's 'Select PHP Version' tool was set to v7.1 but multiple WordPress diagnosis tools were detecting v5.6 was actually running, and they also detected file system issues.The File Manager tool in cPanel showed all the permissions were correct, and the folders were writeable.One of the diagnosis tools I used was part of the Wordfence plugin. It was available on the Dashboard menu at Wordfence Tools Diagnostics (tab).I reported the issue to the hosting company, and it appeared to fix itself overnight (the person who responded to my support ticket indicated they didn't fix anything).
![]()
I think it's likely it was a symptom of a problem that affected multiple hosting accounts, and somebody else within the hosting company probably detected it and fixed it.In case others encounter a similar issue, I hope this answer helps them spend less time trying to track it down. Once I discovered the incorrect PHP version appeared to be running, I figured it was probably not something I could fix with only cPanel access.
![]() Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
February 2023
Categories |