We recently worked on a website project for a client who has been using WestNet Hosting in Australia, and met some problems that we have never met in our development life... So read this article before you choose WestNet Hosting if you are in Australia.
Obviously the server we have been working on was not set up with the right user permission group. But just such a simple problem, which could be done by their system administrator in minutes, gaves us the idea what the shared host clients like our client deserves to hosting companies like WestNet Hosting...
1. After the website is deployed/moved from our developing host, we were surprised finding that any action that Joomla requires file rewriting can not be done. Joomla SH404 not working, DocMan backend file upload not working, and even change of system configuration not working.
2. Then we checked the Joomla system information, and found none of the file folder has the permission to rewrite (unless we change these folders into permission 777). Also before this project a hacking file was planted by a hacker through web end and we could not delete the file through the FTP. Deleting such a file from the server is not a big challenge to us. But no rewriting permission?
3. Then we checked and did tons of tests on the server, and found any file that transferred through FTP can not be written by the web end. We guess it is because the FTP user does not belong to Apache group.
Now the funny story begins.
We tried to call them 3 times, got 3 different answers:
1. The first guy told us, if changing the folder permission into 777 will make the website work, then just change it into 777. I got a lol for this answer, and hung off the phone with a sigh.
2. The second guy told me, we need to enable the FTP config in Joomla. But the problem is, to enable that has no business with the permission problem at all, and, due to the problem of permission group, even if we enable that, the config file does not work (because the server does not allow us to apply the changes due to the permission error).
3. The last guy, told me that their FTP system is separated from Apache and they can do nothing. He told me the FTP user should be in Apache group by default. Then tell me if 777 works then it is the Joomla system problem, not theirs. For the god sake I can not figure out a correct logic here as these answers are conflicted... So if 777 works, then the program itself has a problem? The last sentence he told me was that he can not help, and his call time is limited due to their company policies... This last guy, he did not even check the username of the share host we use.
Well after spending over one hour, we did not get a precise answer to tell us what to do, neither they did not even spend a second to check if their system is set up correctly.
What we were also worried, is that if any of the virtual host on the same IP, is having the same trouble as we met, and followed their suggestion of turning file folders into 777, then once this virtual host is hacked, the rest will be down too.
So this is the story, the first 2 guys were in good attitude at least, but not helpful and the last guy was just bullshitting. Another host, called innet, is actually the same group of guys with this WestNet Hosting. Check their websites http://www.iinet.net.au/ and http://www.westnet.com.au... They are both using the same hosting system Parallet Automation. We did a project on iinet share host before but totally had no problem like this.
What we are not comfortable with is not only the setting problem, but actually how unprofessional they are and how funny their replies to such problems, I guess especially to share host users as they are the "small clients" in their mind.
This is the worst server experiences we have ever had. Good bye WestNet Hosting!