Hack Forums
You don't have permission to access / on this server. - Printable Version

+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Webmasters (https://hackforums.net/forumdisplay.php?fid=141)
+---- Forum: Website Construction (https://hackforums.net/forumdisplay.php?fid=50)
+---- Thread: You don't have permission to access / on this server. (/showthread.php?tid=4444534)



You don't have permission to access / on this server. - VipVince - Sep 13, 2014

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:

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.


* - Dennis - Sep 13, 2014

Could be literally everything... documentroot in the vhost right? Document disallow in vhost maybe? Does the folder still exist? Symlinks wrong? Chmod right? Does the user running the Apache have access to documentroot?


* - VipVince - Sep 13, 2014

It is still giving that error.

As I said, I cannot access the server until I am back at work. I am concerned that it is giving me that like 2 days after building it again.

It does appear like they have changed hosting server though, as its went from being on a domain with 7 other websites, to 999+. Strange.