Update Failure – permissions issues (conflicting solutions)

That is definitely a problem your hosting provider will need to either correct or provide more details on.

If recommend contacting your hosting provider’s support again and asking to speak to someone higher up the chain.

Is that while doing the update from the WordPress admin dashboard?

Are you running a security plugin that possibly modified your file permissions?

Did you modify file permissions somehow maybe per someone’s instructions? Or a document? Maybe something like this? https://codex.www.ads-software.com/Hardening_WordPress

Here’s a bit of info about the proper settings for file permissions… https://codex.www.ads-software.com/Changing_File_Permissions

They’re saying it’s wordpress issue and that I need to check with WordPress to see what the permissions/owners are on that file (update-core.php) and match that with the account holder?

Or have wordpress tell me which files need which R-W-X permissions assigned to them.

2nd Issue that may help me. How can I upgrade my wordpress account from free to a paid business version to get access to live chat?

Yes JNashHawkins,

We have WordFence on the site.

File permissions should be 644 for files and 755 for directories.

You _may_ need to set directories to 777, but that would just mean that the server is misconfigured and PHP is running under the wrong user. If that is the case, I recommend consulting your hosting provider’s documentation or support to properly fix that, but setting the directories to 777 is indeed the faster (though less secure) fix.

https://codex.www.ads-software.com/Changing_File_Permissions

2nd Issue that may help me. How can I upgrade my wordpress account from free to a paid business version to get access to live chat?

www.ads-software.com doesn’t have any such upgrades. The software here is provided for free, and built and supported entirely by volunteers.

WordPress.com is what you’re referring to.

To clear up any confusion, WordPress.com and www.ads-software.com are two different entities: https://codex.www.ads-software.com/WordPress_vs_WordPress.com

ok. Thanks James,

background: I’m taking over IT duties at a company and just trying to make heads or tails of how things are set up and also sort of new to website stuff.

I’m FTP’d to the webserver what would be the path to the Folders/Files.

srv/www/xxxxxxx/public_html/wp-admin (or /wp-content or wp/includes) ?

or is there a different path that I am not even close to?

Do I globally change all those folders to 755 (or 777) and all the files in those directories to 644?

Any more help would be greatly appriciated.

Based on what you described, all of the WordPress files are under srv/www/xxxxxxx/public_html/

All files in there should be 644, and all folders in there should be 755.

Ok. I applied 755 and 644 to everything in there and got the same error.

Any other suggestions. File ownership issues? Should I disable WordFence and the All in one WP security plugin which I also have activated?

I’m at a loss. ??

Yeah, might as well see if that makes a difference.

Sometimes, when I suspect it’s going to take a bunch of time and effort to fix issues that might actually be beyond the minuscule cost of buying a little more server space… especially on a shared host…

I’ll grab a new account, hit the one button installer while telling it to duplicate my current install’s directory structure… either root install or sub-directory. Copy over the theme(s), plugins and media files.

Now make a copy of the new server’s wp-config and then copy the database credentials, change the database server name to the server of the old database and copy over any other remarkable points into config.

Now try to bring the site up by changing the DNS A record… you might have to tell the old server to share the remote MySQL.

If all is well the update probably was done during the one button install or can be done now. Do a backup or everything including the database. Swap the config and then restore the database. You’ll be on the new site’s database after the config swap so the restore finishes the move.

Give it a day or so to make sure you didn’t forget anything then kill the old server account.

Sounds really complicated but with the ‘Famous Five Minute Install’ this only takes a few minutes total. I swap out server accounts after about three years max anyways.

Thanks everyone for your input.

Turns out I was given the wrong site to access. We still may need to fix this, but it’s not as crucial as what I’m doing now with the newer site.

I will open another ticket about the Google API / Store Locator Plus plugin errror that I’m experienceing now.

Thanks again.