These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Can't access Joomla domain converted from plesk on the new forum.
Web Hosting and Cloud Computing Control Panels
That depends on whether you are running it under mod_php (as apache) or fcgid (as domainuser)
If fcgid
as root in /home/domainowner
chown -R domainowner:domainowner /public_html
as root in /home/domainowner/public_html
chmod -R 755 *
chmod -R 644 *.php
If mod_php
same, but you'll have to change ownership to apache:apache for any file or directory that needs writable by Joomla (e.g. configuration.php /images/ /components/ /templates/ -- the full list of what needs writable can be found in the Administrator > System > System Info
Bottom line is, Joomla is much easier to work with in fcgid because the permissions will dumbfound you if you don't know what needs what.
It's usually easiest to install and begin a PHP site with fcgid, then when you get it all tweaked out and want to run it under mod_php for better security, performance, memcaching, etc. then you can switch the PHP setting for the domain and fix the ownerships and permissions. It's likely you'll want to do that to make it more secure if you are going to be running a site that needs better protection and performance.
If you just need to get a simple site running for a client, and you are providing hosting services to multiple customers, then fcgid is definitely the way to go, as it is so much simpler. It is just so much easier to install components, plugins, write config files, etc. when all are running as the domainowner and you don't have to deal with ownerships and permissions.<br><br>Post edited by: PlayGod, at: 2008/04/05 19:14
<div class='quote'>It's usually easiest to install and begin a PHP site with fcgid, then when you get it all tweaked out and want to run it under mod_php for better security, performance, memcaching, etc.</div>
While most of this advice is excellent, I'll point out that mod_fcgid+mod_suexec is always more secure than mod_php. There are no circumstances where this would not be true. The only occasion where this wouldn't be true is if a security bug were found in suexec. Since suexec has gone literally years without security issues, and mod_php has several security bugs in every year for as long as it has existed, I believe I am safe in suggesting that suexec is always more secure.
Otherwise, you're spot on. Permissions are the tricky bit, and it'll depend on a lot of factors what the right path to getting things running again is. The documentation is probably worth consulting, as well, specifically the troubleshooting guide:
http://www.virtualmin.com/documentation/id,troubleshooting_common_proble...
--
Check out the forum guidelines!
I get that it is more secure... but I have atleast one site where php can't run as a cgi.
is there some documentation detailing how to get scripts in virtual domain to run under mod_php?
Thanks
<div class='quote'>is there some documentation detailing how to get scripts in virtual domain to run under mod_php?</div>
There's not much to document. You just switch execution modes. ;-)
Select the virtual server in the dropdown list.
Click on "Website options" in the Server Configuration menu.
Select "Apache mod_php (run as Apache's user)"
Save it.
Fix permissions and ownership, as needed. (This can't safely be automated.)
Out of curiosity, what prevents the site from running under CGI or mod_fcgid? (Noting that mod_fcgid is roughly identical to mod_php in performance, though possibly slightly more memory intensive for a very heavily loaded application. For lower load environments, removing mod_php from Apache and running everything under mod_fcgid is actually more memory efficient and equally fast.)
--
Check out the forum guidelines!
you know.... I can't remember :<(
I have been learning amfPHP and thought there was something there that didn't work but I can't find the reference.
Oh well for now I will leave it.
Thanks
Todd