Sep 13, 2014 03:02 AM
(This post was last modified: Sep 13, 2014 03:06 AM by VipVince.)
This has me concerned.
It is a website I set up for a client; basically it appeared to have been hacked before as I found several shells on the site.
I removed the shells, upgraded the CMS to the latest version, changed passwords, and a few other things. It's hosting had disabled the website due to the fact that there was shells being hosted on it.
I had to set it up again, after removing the files, and tightening it up. I literally only set it up live two days ago, and now I am getting this:
I must mention, it appears it has changed hosting however. A couple of days ago, it was on a site with 6 or 7 other websites, and upon checking today it is on a server with 999+ websites.
That has me asking, is the server migration the issue, and a .htaccess is causing this Apache error? Or has the previous hackers rm rf /'d the public_html. It would be surprising if the latter was the case, I had it pretty secured and it was only up for 1/2 days.
It is a small website so would they really be sitting and waiting like the second scenario would suggest? It was down weeks before I set it backup.
Just trying to determine the problem, I will not be able to contact the owner to Tuesday, nor can I access the server from home. It is all done through work.
Opinions are welcome.
It is a website I set up for a client; basically it appeared to have been hacked before as I found several shells on the site.
I removed the shells, upgraded the CMS to the latest version, changed passwords, and a few other things. It's hosting had disabled the website due to the fact that there was shells being hosted on it.
I had to set it up again, after removing the files, and tightening it up. I literally only set it up live two days ago, and now I am getting this:
PHP Code
<?php
Forbidden
You don't have permission to access / on this server.
Apache/2.4.9 (Unix) Server at www.website.com Port 80
I must mention, it appears it has changed hosting however. A couple of days ago, it was on a site with 6 or 7 other websites, and upon checking today it is on a server with 999+ websites.
That has me asking, is the server migration the issue, and a .htaccess is causing this Apache error? Or has the previous hackers rm rf /'d the public_html. It would be surprising if the latter was the case, I had it pretty secured and it was only up for 1/2 days.
It is a small website so would they really be sitting and waiting like the second scenario would suggest? It was down weeks before I set it backup.
Just trying to determine the problem, I will not be able to contact the owner to Tuesday, nor can I access the server from home. It is all done through work.
Opinions are welcome.