Disaster! Cannot edit .htaccess

[almarma73]

Disaster!! After testing my free subdomain and ckeching that everything was alright, I decided to change my domain to the x10 free hosting. Well, today, just after enabling it and starting to test it, wanted to enable W3 Total Cache, a plugin for WordPress that improves performance a lot and reduces the server consumption. But now, after enabling it, I'm continuously suspended by high CPU usage, and also the .htaccess cannot be modified, neither by WordPress and me using Cpanel or FTP (Operation No Permitted). Why I cannot edit my .htaccess?

---------- Post added at 11:09 AM ---------- Previous post was at 09:05 AM ----------

Ok, I'm moving back to 000webhost, sorry. I have just had one morning with my website on x10, and I have about 15 "suspended" issues in just one morning, with about 1-3 visitors per day. I cannot imagine what will happen if I receive more visitors... It's very sad, because I really like how fast it works, but I cannot live in the hosting page, I have more things to do the rest of the day

 

[callumacrae]

You started a thread here: http://x10hosting.com/forums/free-hosting/133676-htaccess.html

Total Cache would only make it use more resources, it'll make it worse.

~Callum

 

[almarma73]

Yes, I know, thank you. I started it after this post, because I found the support tickets feature. Sorry. Anyway, the suspensions keeps happening after disabling total cache

 

[callumacrae]

Wait for the ticket to be replied to, don't ask here

Be aware that a lot of the plugins with WP use a LOT of resources - almost all of the high resource usage suspensions I see have WP installed. Try disabling a couple ones, like any caching plugins.

~Callum

 

[str82u]

I don't know if you already did this, but ask the tecks if they can pinpoint the issue for you, maybe get you a copy of an error log so you can get a handle on it. Hosting techs are usually my best source of information when I need to edit or tweak something or if there was a problem users/ip address.

I host both places, 000 and x10. I wouldn't leave either of them and defend them to others if it comes up. Next time you plan a move, I'd set up the destination first if possible before changing NS, on the subdomain, then bring the TLD over.