PS on dedicated server permission problem

[VoyageGroupe]

I have a problem with installing PS 1.5.6.1 on GoDaddy dedicated server.

First I moved all files through FTP. All files was under user @USER@.

Installed, on step 3 got error about "need recursive write permission on directory: config, img, download, cache, modules, etc"

I changed all files and directories to 777 (just to install) (before it was 755), installation was successful.

Changed all directories back to default 755 and started getting error: Fatal error: Uncaught exception 'SmartyException' with message 'unable to write file /var/www/vhosts/mysite.com/smarty/ ... 

Checked files under FTP - many of them was under @Apache@ user.

Somehow I got access to back office, but next movement lead back to same fatal error.

After that I was not able to delete or modify any files under Apache user.

I changed all files through SSH to my @USER@, deleted, changed PHP support run as FastCGI application.

Installed prestashop again - everything went sucesfully. But now then I am trying to upload theme - 500 internal server error. 

Changed FastCgiRequestLen to biggest size - no results at all.

I am confused :\

Is it anybody know how to do it correctly on GoDaddy dedicated server? The GoDaddy technical support is useless :|

Thanks.

 

[doekia]

You need recursive ...

cd /your-install-path

chown -R @user@ .

 

If problem persist, PM me with your ssh access, I'll fix it for you

[VoyageGroupe]

I thought about it. But I think it will change permission only on existing files, but all new files will be created by PHP under Apache user again. And with time it will became same problem. It is not correct?

[doekia]

Not because usually (unless you have made a weird install) your apache user should be the same as your @user@.

 

If not the case (and that is a pretty big security breach) you have to do a chmod -R a+w .

[msk69]

I have a problem with installing PS 1.5.6.1 on GoDaddy dedicated server.

 

Ask them to install mod_ruid2 or SuPHP, and you do not worry about permisions anymore. Makes it much easier to handle installations.

[El Patron]

Not because usually (unless you have made a weird install) your apache user should be the same as your @user@.

 

If not the case (and that is a pretty big security breach) you have to do a chmod -R a+w .

 

I agree.

 

When you define the domain on your dedicated server with either cpanel or plesk (these two for sure).  The owner should be set to yourdomainname (without the www).

 

if you create the root domain permissions manually, then the owner of the files is id of person logged into control panel.  You would then need to change all files in the folder (or root) to that of the domain.

 

Is a shop owner has to change 'anything' to 777 to get 'something' to work.  They have something wrong in their initial site file generation.  my two cents

[VoyageGroupe]

Not because usually (unless you have made a weird install) your apache user should be the same as your @user@.

 

If not the case (and that is a pretty big security breach) you have to do a chmod -R a+w .

 

 

I agree.

 

When you define the domain on your dedicated server with either cpanel or plesk (these two for sure).  The owner should be set to yourdomainname (without the www).

 

Thank you guys very much for help, but still confused. Server was installed long time ago before me, probably the users is messed up. It is plesk. Just spoke with godaddy support:

"Okay. Most of the time this happens because you have PHP support running in Apache mode instead of FastCGI.

If you're in Apache mode, any changes take root ownership.

Unfortunately this is just how Plesk is built. If you want to be able to access within Plesk you need to have it as FastCGI mode.

You'd need to ask the developers of Plesk that question, I don't know why it acts this way, I just know that's what happens.

If you want to be able to have access to all files in Plesk without permission issues, you're going to need to run in FastCGI mode. I don't know of any work around for that."

 

So he is telling me that I MUST to use FastCGI instead of Apache. But I do not understand how so many people using Prestashop on Apache without any problems at all.

So I have 2 questions: 1) How I can fix 500 internal server error in PrestaShop in FastCGI mode   

OR 

2) How can I fix user permission issue under Apache mode?

Looking right now about SuPHP, is it any different way to fix it?

Found one more way to fix it: http://www.prestashop.com/forums/topic/226561-solution-for-recursive-write-permissions-on-files-and-folders-error/    Is it safe and correct way to fix that problem?

Thanks.

Edited December 12, 2013 by VoyageGroupe (see edit history)

[doekia]

If you are running mod_php then simply change ownership recursive to be www-data:www-data (the usual webserver daemon user)

 

chown -R www-data:www-data .

 

And you have to do such everytime you transfert something with FTP

[VoyageGroupe]

If anybody will have same issue later: I resolved it by changing server to FastCGI Mode and increasing MaxRequestLen on php settings at the /etc/httpd/conf/