Permissions for Wordpress install

cyberpoint said 2 years, 7 months ago:

I’ve searched as much as I possibly can to find an answer before posting this plea for help.

I’ve added a domain to my VDL server, added a MySQL database, user, etc, etc, and uploaded the latest version of WordPress.

It installs and runs fine. Except, while logged-in to WP as the admin and trying to add an image to a new page I’ve created, I keep getting a message that it was unable to move the file.

So I can create and edit new content.

But I can’t add an image.

Nor can I edit and save the theme files as they don’t have the necessary permissions either.

Anything to do with the database works. But anything that needs write permission on actual files does not. Plainly I don’t want to chmod all my directories and files to 777!

It *seems* to me that WP is running as the wrong user and is only picking up the group permissions, not the owners. I have tried uploading WP using the root admin login (thinking it might inherit the right permissions) but that makes no difference.

Anyone got any ideas?

Deleted User said 2 years, 7 months ago:

@Cyberpoint,

Have you tried re-installing WordPress all together? It sounds like something got jammed up during the installation. If not, I would try that and then go from there. If you continue having issues, please post the exact error you’re getting and we’ll look further into this. Thanks!

-Clint

cyberpoint said 2 years, 7 months ago:

Hi Clint,

Thank you. I have tried installing it and re-installing it on three domains now, being careful to note precisely that I’m doing everything I think is required.

The thing it, WP appears to work correctly, but when I try to add an image in a post, using the java upload or the browser upload, it *appears* to be uploading something (and perhaps putting it into cache) then I get this message:

“image-01.jpg” has failed to upload due to an error
Unable to create directory /home/bucksadmin/public_html/wp-content/files/2010/09. Is its parent directory writable by the server?

I have tried creating the directory manually, but it still fails to actually write the file.

If I go to Themes, and click on editor, it brings up the various php and css files, but this message appears at the bottom:

You need to make this file writable before you can save your changes. See the Codex for more information.

If I chmod any one of them to 777 I can then edit and save it.

Happy to do or redo anything you want.

cyberpoint said 2 years, 7 months ago:

Hi Clint,

Just a gentle reminder – I know you’re busy but I’d really like some help on this as I do need to find a fix.

Cheers, Mark

cyberpoint said 2 years, 7 months ago:

This is curious, the counter says there are five posts on this topic, I can see my three, and one from ClintS but nothing else. I’ve reloaded, refreshed, re-navigated to the page, is something wrong with my maths?

chrisg said 2 years, 7 months ago:

Dear Cyberpoint,

I have reviewed this matter with our Server Support team. The error you have described does confirm a Permissions related error. The problem is that WordPress is running as Apache and trying to write to directories owned by the FTP User.

To best address this error, it is recommended that you install and configure suPHP. Then the application scripts would run as the same user that FTPs the files up to the server.

As for the post counts of this topic, we are aware of issues occurring on some topic threads that are displaying one additional post that was not posted. It is a rare occurrence, and we are doing what we can to prevent this from occurring on future threads.

Christopher G.

cyberpoint said 2 years, 7 months ago:

Okay, thanks for the advice Chris.

I’ve done a lot of reading-up, and before I start doing some pretty fundamental things, such as rebuilding Apache, I need to ask a few questions.

I don’t have this problem with other hosting packages I have with Go Daddy. Why is that? I can do exactly the same thing with them that I’m trying here – namely install WordPress and run it “out of the box”.

Why does WP try to run as Apache when I have uploaded it as myself as root user, or another user I have created? Surely this is a bug with your set-up?

If I install suPHP and rebuild Apache, am I now running a non-standard version of Apache?

What happens when a bugfix comes out and you want to update Apache?

What happens if I need you to reboot or reprovision the server? Do I have to reinstall my mods and rebuild Apache again?

Am I your only customer to have experienced this issue?

I you accept this seems to be a hosting configuration problem, will you fix it?

Cheers, Mark

cyberpoint said 2 years, 7 months ago:

Hi Christopher,

Thanks for investigating this.

Before I do anything as drastic as rebuilding Apache, I need to ask a few questions.

I can install WordPress on other hosting accounts I have with Go Daddy and these work as required, “out of the box”.

Why does WP run as Apache in the first place, when I have tried uploading it with my root account or as another user I have created?

Am I the only customer who seems to be having this problem?

Is this a problem with how you have the server configured?

If I install suPHP and rebuild Apache, do I now have a non-standard Apache installation?

If I need to ask you to reboot or reprovision the server, do I have to reinstall my mods and rebuild Apache again?

What happens if there is an Apache mod and you need to upgrade Apache?

If you accept this is a server configuration issue, will you fix it?

Cheers, Mark

cyberpoint said 2 years, 7 months ago:

(posted again as it seems to have disappeared)

Hi Christopher,

Thank you for looking into this problem.

Before I do anything as drastic as rebuilding Apache, I need to ask a few questions.

I can install WordPress on other hosting accounts I have with Go Daddy and these work as required, “out of the box”.

Why does WP run as Apache in the first place, when I have tried uploading it with my root account or as another user I have created?

Am I the only customer who seems to be having this problem?

Is this a problem with how you have the server configured?

If I install suPHP and rebuild Apache, do I now have a non-standard Apache installation?

If I need to ask you to reboot or reprovision the server, do I have to reinstall my mods and rebuild Apache again?

What happens if there is an Apache mod and you need to upgrade Apache?

If you accept this is a server configuration issue, will you fix it?

Cheers, Mark

cyberpoint said 2 years, 7 months ago:

Curious again. I post a further reply, it says it’s being held for moderation, then after a while that message disappears and I never see my reply.

Try again:

Hi Christopher,

Thank you for looking into this problem.

Before I do anything as drastic as rebuilding Apache, I need to ask a few questions.

I can install WordPress on other hosting accounts I have with Go Daddy and these work as required, “out of the box”.

Why does WP run as Apache in the first place, when I have tried uploading it with my root account or as another user I have created?

Am I the only customer who seems to be having this problem?

Is this a problem with how you have the server configured?

If I install suPHP and rebuild Apache, do I now have a non-standard Apache installation?

If I need to ask you to reboot or reprovision the server, do I have to reinstall my mods and rebuild Apache again?

What happens if there is an Apache mod and you need to upgrade Apache?

If you accept this is a server configuration issue, will you fix it?

Cheers, Mark

cyberpoint said 2 years, 7 months ago:

Is there a problem with posting to this board? I keep trying to post this:

Hi Christopher,

Thank you for looking into this problem.

Before I do anything as drastic as rebuilding Apache, I need to ask a few questions.

I can install WordPress on other hosting accounts I have with Go Daddy and these work as required, “out of the box”.

Why does WP run as Apache in the first place, when I have tried uploading it with my root account or as another user I have created?

Am I the only customer who seems to be having this problem?

Is this a problem with how you have the server configured?

If I install suPHP and rebuild Apache, do I now have a non-standard Apache installation?

If I need to ask you to reboot or reprovision the server, do I have to reinstall my mods and rebuild Apache again?

What happens if there is an Apache mod and you need to upgrade Apache?

If you accept this is a server configuration issue, will you fix it?

Cheers, Mark

cyberpoint said 2 years, 7 months ago:

Hey, there they all are…

cyberpoint said 2 years, 7 months ago:

Note to moderator: Thanks for tidying up

cyberpoint said 2 years, 7 months ago:

Hi,

Can anybody help? I really need some answers to my questions above.

Thank you, Mark

Deleted User said 2 years, 7 months ago:

Hey Mark,

The issue you’re having is because you’re missing SUphp. The default Apache configuration will always run as Apache and a reboot will not have any affect. You’re definitely not the first person to have these issues, however, most users do not use suPHP to run their sites and that is why it’s not included by default. In this case, you’ll need to re-provision your server and install suPHP. Our Expert Hands team can also help you with this. You can find out more information on this team here:

http://support.godaddy.com/help/article/2887

Sorry for the delayed response. Hopefully this will answer your questions!

-Clint