Please help - Cpanel Problem

Tweep Cat · #1 (**permalink**) 10-18-2009, 05:59 AM

I have recently moved to a new server, both were using Cpanel.

On the old server I was able to install phpbb3, Automod and Mods onto Automod fine.

On the new server I am having some issues that are making running a forum very hard. When I installed the phpbb3 board I had to change permissions of the config.php to 777 before it would let me write anything. When installing the Automod it asked for the ftp so I entered the details that I use to log into my cpanel. I also had to change a directory to the 777 permission so that it would be able to write to install Automod. I tried to install mods with the Automod and on the new server and it asked for the ftp so I entered my cpanel login details. When I did it said 'Unable to change directory'. The ftp was correct I think, as if I entered wrong details it said it was wrong.
None of this happened on the old server - I wasn't asked for ftp and the files were able to write properly.

I also tried installing mybb but it said: http://i38.tinypic.com/14ohlh.jpg

I also tried smf which installed fine, but the mods didn't seem to upload properly which I think might be the same issue as the phpbb3 forum and Automod.

I posted this here and not in the forum area because I think this might be a problem or a setting to do with cpanel not the forum software because it worked fine on the old server.

Is there a setting on cpanel that could help me, because I can't install anything such as mods and some forums properly?

vectro · #2 (**permalink**) 10-18-2009, 06:49 AM

Did your last server use any Apache modules like fcgi or php-cgi? Those are modules that causes a PHP script to run under the username who owns it instead of running under the 'nobody' username that Apache uses. This means that PHP will only allow the user who owns a file to write to it. It is good for security and also prevents the need for files to be chmod 777 to be written to. If your old server uses one of those but the new one doesn't, that would explain why your old server didn't have these problems.

websiteguy · #3 (**permalink**) 10-18-2009, 06:56 AM

you can discuss this with support of your host. I am sure you will get some solution.

Tweep Cat · #4 (**permalink**) 10-18-2009, 07:02 AM

Thanks.

Would it work if I changed all of the files to 777 while installing mods on Automod and then changing them back to their previous settings? Or wouldn't that make any difference?

vectro · #5 (**permalink**) 10-18-2009, 07:12 AM

Changing them all to 777 is highly insecure as it makes files world-writable. Once you change them all to 644 any files that that need to be written to won't be able.

Tweep Cat · #6 (**permalink**) 10-18-2009, 07:15 AM

Quote:

Originally Posted by vectro

Changing them all to 777 is highly insecure as it makes files world-writable. Once you change them all to 644 any files that that need to be written to won't be able.

But would it work if I change them to 777 while installing stuff then changing it back to 644?

vectro · #7 (**permalink**) 10-18-2009, 07:21 AM

Quote:

Originally Posted by Tweep Cat

But would it work if I change them to 777 while installing stuff then changing it back to 644?

Theoretically, yes. When you change back make sure that any files that need to be written to in the future remain 777.

I'm trying to get to the root of the problem, though. If you can get there then you won't have problems in the future and will be able to install what you need. It sounds like an issue with permissions and that your new server is handling PHP requests differently than the last one. When putting those two factors together it seems like you're missing a module that runs PHP as CGI (since that relates to both permissions AND how PHP is handled).

icebreaker · #8 (**permalink**) 10-18-2009, 07:50 AM

Quote:

Originally Posted by websiteguy

you can discuss this with support of your host. I am sure you will get some solution.

This is the right thing to do. Any technical problems that you encounter must be resolved immediately by getting assistance from the technical support of your web host company.

**ScriptMan** · #9 (**permalink**) 10-18-2009, 11:19 AM

Many times 744 or 755 will work where you think you need 777. Either is slightly more secure.

I would hesitate to use a script that needed 777 as an ongoing event.

As noted above this isn't really a cPanel issue. It is something in the server configuration. My first guess is the old server was using suexec and the new is not.