Web Hosting Talk : Web Hosting Main Forums : Hosting Software and Control Panels : How to suspend user without suspendind cpanel account

[Vans]

Hi,

Anyone here know how it's possible to suspend a website on WHM in keeping the customer to use his cpanel and ftp access ?!



Thanks

[daimon666]

Can you explain the circumstances why you need to do this? Not being noisy but help come up with an answer for you.

[sysguru]

simple rename index.html, this will be enough to take his site down.

[Patrick]

1. chmod 000 public_html
2. chown root:root public_html

That will prevent files under public_html from being served, and prevent them from enabling it again.

[anythingss]

every option i could think of (including the ones mentioned above) allow the user to un-suspend themselves if they wanted.
which brings me to daimon666's question

[dhcart]

You can disable a file or directory by changing it's permission.

[KMyers]

Hello,
You could try creating the following .htaccess file containing. It would cripple anything in the webroot. This however would still allow any outbound scripts to work.

Redirect 301 / http://domain.com/cgi-sys/suspendedpage.cgi

[Vans]

Sure,

I have a customer that his website overload my server at 600% due at a script php problem... I want allow him to fix the problem to get his website back online. I have suspended his account because if the account is active the entire server crash.. so what i can do for allow the customer to make the change of his website without see his website online.

Thanks for your answer

[HostingOwner-SS]

create .htaccess file and past the following code.

single ip address access

order deny,allow
deny from all
allow from 192.168.1.1

http://www.yourdomain.com/.htaccess

multiple ip address access

order deny,allow
deny from all
allow from 192.168.1.1
allow from 192.168.1.2
allow from 192.168.1.3

Authorize the ip for your client only he will be able to access site without any problem no one else.

[linux-tech]

Originally Posted by anythingss

every option i could think of (including the ones mentioned above) allow the user to un-suspend themselves if they wanted.

No they don't (or they shouldn't).
If you change ownership of public_html to root:root, nobody should be able to change that back.

.htaccess files will be easily removed by the user, theoretically.

If you want to REALLY suspend things (without suspending the account):

chown root:root /home/username
chmod 000 /home/username

This way, even if they can login (they can), they can't change anything back to themselves, or shouldn't be able to.

[anythingss]

Originally Posted by linux-tech

No they don't (or they shouldn't).
If you change ownership of public_html to root:root, nobody should be able to change that back.

.htaccess files will be easily removed by the user, theoretically.

If you want to REALLY suspend things (without suspending the account):

chown root:root /home/username
chmod 000 /home/username

This way, even if they can login (they can), they can't change anything back to themselves, or shouldn't be able to.

proftpd running without pam (such as the config cpanel does) allows you to do many things to override file permissions, regardless of their ownership or permissions.

#touch testfile
#chmod 000 testfile
#chown root:root testfile

ftp> Command: DELE testfile
ftp> Response: 250 DELE command successful

#ls testfile
ls: cannot access testfile: No such file or directory


edit: i think its the lack of pam that allows it to happen, not sure tho.

[linux-tech]

all the more reason to switch from proftpd.
If you follow the advice about chmoding /home/user and changing ownership, the user has nowhere to login to, even with ftp programs