Can't Set Up Redirects

Status
Not open for further replies.

klowl

New Member
Messages
10
Reaction score
0
Points
0
When I try to set up a redirect through C-Panel, I get the following error:

Code:
Unable to write to .htaccess: /home/nccyc/public_html/.htaccess

I've seen elsewhere that I should try to edit permissions for that file, but I don't know what to change them to, and even when I try to change them it won't let me. One place said that I needed to make sure that "System" was set for read/write permissions (the numbers would be 0644), but there isn't even a "system" column, just "user," "group," and "reader" (which is currently set to 644).

What can I do to restore this capability?
 

Livewire

Abuse Compliance Officer
Staff member
Messages
18,169
Reaction score
216
Points
63
Fixing it now, give me about 5 minutes; somewhere in there your user account lost permissions to the .htaccess file.


Edit: Try now. By "lost permissions" I don't mean the actual permissions were wrong (they were 644), but somehow you were no longer the owner of the file, hence the problems. Easy enough to fix from here though :)
 
Last edited:

Livewire

Abuse Compliance Officer
Staff member
Messages
18,169
Reaction score
216
Points
63
Would the system do this during a Suspension/Unsuspension ?

*snip*

So while unlikely, that probably -is- the cause. I can't think up anythign else that would've done it :(


Edit: Yeah, watched it while I suspended my test account, that is what caused it. The contents of the file are right but it forgot to change the owner back; if you read this -before- the edit, ignore what I had said above, as it doesn't apparently work that way once I looked closer :)
 
Last edited:

klowl

New Member
Messages
10
Reaction score
0
Points
0
Thanks. It all works now. And, yes, I suspect it was from a recent suspension. I got suspended for excessive resource usage, but I'm still not really sure why. Any thoughts?
 

Livewire

Abuse Compliance Officer
Staff member
Messages
18,169
Reaction score
216
Points
63
If you have any caching plugins disable them; those are notorious for hogging cpu when generating the cache.

Otherwise, look for anything that could use excessive CPU/Ram for an extended time, such as scripts on a cron.
 
Status
Not open for further replies.
Top