The Uploaded File Could Not Be Moved to Wp-content No Shell Access

At some point in your WordPress admin career and ESPECIALLY if you are in the concern of migrating websites from one server to another you will EVENTUALLY run across this error message when attempting to add images to your media library:

"<paradigm-proper noun> has failed to upload due to an error. The uploaded file could not exist moved to wp-content/rest-of-path-hither"

An additional side consequence of this same error is that fact that you are NOT able to automatically update existing plugins OR add new ones. When you lot try to add a new plugin (for instance), WordPress volition gracefully present you with an FTP credentials screen then that you lot tin can manually upload the new plugin. And then…..

WHY IS THIS HAPPENING?

In MOST instances, (especially in the case of a MIGRATED website which was already running without issues on another webserver) what is happening is that WordPress passes off the FETCHING (or uploading) of the requested image to the web server process on which your website resides and it happily retrieves the image.jpg from your harddrive and uploads to temporary memory of the server THEN tries to commit the file into storage of the WordPress media library (which is most often /wp-content/uploads/<year>/<mo>). This of course is where the error occurs. The business relationship that actually RETRIEVES the file from your estimator is the Apache service account and many times the NOBODY account (yes, that IS the existent name of the account) on the server itself. Since that particular account has NO OWNERSHIP or rights to the /wp-content/uploads/<year>/<mo> folder… you lot get the nice error message indicating at that place was an issue placing the image in that particular binder. THIS IS BY DESIGN PEOPLE … and it means your web server is simply enforcing the security parameters it is aware of…. Which is a adept thing!

SOME Really BAD ADVICE

So similar whatever other adept WordPress admin and to attempt and resolve this effect, you copy – paste – and Google. What you will find withal should not merely SHOCK you lot but should make the pilus on your security-censor cervix stand up up! ix out of ten "recommendations" on how to resolve this trouble involve setting the permissions on your /wp-content/uploads folder to 777!!! … to that I say NO – NO – NO! If you're going to practice that you might equally well change the password to your "admin" account to 12345 as well!

SO LETS INSTEAD Actually Prepare THE Effect… THE PROPER Manner

STEP 1: Find out which business relationship on your server is the Apache Service Business relationship – Unfortunately, this part is non always like shooting fish in a barrel for those with a shared hosting account and NO shell (sometimes chosen SSH) admission to their site. UPDATE: Run across the link provided below by jervisbay in the comments department on how to fix this issue in a shared hosting environment. Thx jervisbay! The intimidation factor is that trounce access is a basic command line interface… you know, the quondam black screen with white text and a command prompt… YUCK! Withal, if you DON'T take this blazon of access… just email your hosting support team with this simple question…What is the name of my website's Apache Service Account? You might also want to say in your email that yous are trying to set the proper permissions on your WordPress installation and that should assistance requite them some context as to your request.

Now… if you DO take vanquish access to your website go ahead and login using a beat out plan like Putty (our favorite). If you are on a VPS or Reseller server, y'all volition likely take access using the <root> user which IS preferred. For shared servers, y'all will probable NOT have trounce access and will instead take to send a support email.

NOTE: The instructions beneath are only for Reseller, VPS, and Dedicated server environments. The reason being is that we are granting admission to a SERVICE running globally on these machine types. This is Non something you'd want to do in a SHARED hosting environment because obviously information technology would open y'all up to a whole new fix of security concerns.

However to go effectually this, shared hosting environments implement a technique called "suexec" which abstracts the account admission yet gives proper rights to enable functionality to piece of work as information technology should. SUEXEC is a topic for another web log mail service discussion, only y'all might want to mention it in your support e-mail (should y'all go that road). Equally a matter of fact, here's a pretty hearty discussion on the topic which you might savour.

Once logged in as root, execute this command:

ps aux | egrep '(apache|httpd)'

This should return output (and a list) like the following:

root      5597  0.0  0.1  70904  6552 ?        Ss   Nov18   2:03 /usr/local/apache/bin/httpd -chiliad beginning -DSSL
nobody    8715  0.0  0.0  69728  2516 ?        Southward    17:xi   0:00 /usr/local/apache/bin/httpd -k start -DSSL
nobody    8717  0.0  0.0  70904  2608 ?        Southward    17:xi   0:00 /usr/local/apache/bin/httpd -yard start -DSSL
nobody    8718  0.1  0.4 1332864 17180 ?       Sl   17:xi   0:06 /usr/local/apache/bin/httpd -k start -DSSL
nobody    8719  0.1  0.4 1333004 17012 ?       Sl   17:11   0:07 /usr/local/apache/bin/httpd -g start -DSSL
nobody    8720  0.1  0.4 1333356 16828 ?       Sl   17:xi   0:07 /usr/local/apache/bin/httpd -k start -DSSL
nobody    8808  0.one  0.4 1333584 16088 ?       Sl   17:12   0:06 /usr/local/apache/bin/httpd -k start -DSSL
nobody   11467  0.i  0.2 1332816 11696 ?       Sl   18:51   0:00 /usr/local/apache/bin/httpd -k start -DSSL
root     11611  0.0  0.0   4052   188 pts/0    D+   18:56   0:00 egrep (apache|httpd)

The account name of nobody (highlighted in black above) indicates that THIS is my apache service account and the one I should grant access to my entire WordPress files in order for life to be good one time again.

STEP two: Grant this user rights to the WordPress install – This procedure is quite simple… just execute the following control within your shell windows:

chown -R nobody /home/<username>/public_html

This of grade assumes that the root of your WordPress installation is inside the public_html binder (quite standard on virtually all CPanel / Linux installations). What this command does is it starts at the root path of WordPress and grants the user called nobody with ownership rights on ALL files and folders RECURSIVELY (meaning it includes sub-folders and files within sub-folders as well) throughout the site.

Trouble SOLVED!

Then that should do it! Now become back to your WordPress admin control panel and endeavour your image upload to the media library over again. You should find that all works without issue (as in the image below). Too, you will now be able to automatically update and upgrade plugins within the site.

johnsonorneved.blogspot.com

Source: https://2surge.com/how-to-fix-the-uploaded-file-could-not-be-moved-to-wp-content-error-message.html

Share this post