Forbidden You don't have permission to access / on this server.

wh33t · 03-31-2014, 01:19 AM

Hey LQ,

So today, for seemingly random reasons my server is not allowing me to view any webpages. It keeps giving me the error as mentioned in my thread title. As far as I know, I didn't change anything to do with Apache that would have caused this and it was working completely fine last night.

Any ideas on where to start?

My server is Ubuntu 12.04LTS. I did not use 'tasksel' to install the LAMP server but followed this guide: http://www.howtoforge.com/ubuntu_lamp_for_newbies

business_kid · 03-31-2014, 02:42 AM

Something is borked. I presume access to / is forbidden anyhow. A full path name might provoke that. Can you ssh in and check permissions? Can you send a hup to aopache, or even restart? Failing that I'd ask whoever has it to reboot it. If you can't see stuff, nobody else can. Then go in with a rootkit hunter such as rkhunter.

wh33t · 03-31-2014, 02:59 AM

Quote:

Originally Posted by business_kid

Something is borked. I presume access to / is forbidden anyhow. A full path name might provoke that. Can you ssh in and check permissions? Can you send a hup to aopache, or even restart? Failing that I'd ask whoever has it to reboot it. If you can't see stuff, nobody else can. Then go in with a rootkit hunter such as rkhunter.

Its a xen vps box. I can ssh into it still. Should I give it a restart and see if that helps?

bulldozers · 03-31-2014, 06:37 AM

One time the same happened to me because of restarting the Apache as a different user. It caused a big mess in terms of config and log files.

wh33t · 03-31-2014, 01:40 PM

Quote:

Originally Posted by bulldozers

One time the same happened to me because of restarting the Apache as a different user. It caused a big mess in terms of config and log files.

Ok well I updated three updates, then restarted. Still can't access anything in the webroot. What should the permissions be for this to work?

My www-root is set to /var/www and my system is a single user root system with out sudo. So root owns and operates everything.

Code:

root@xxxx:~# ls -l /var/www
-rwxrwxrw- 1 root root    0 Mar 29 05:34 index.php
drwxrwxrw- 7 root root 4096 Mar 29 05:34 projects
-rwxrwxrw- 1 root root   25 Mar 29 05:34 robots.txt
drwxrwxrw- 2 root root 4096 Mar 29 05:35 tmp

Habitual · 03-31-2014, 03:58 PM

Quote:

Originally Posted by wh33t

What should the permissions be for this to work?

Code:

root@xxxx:~# ls -l /var/www
-rwxrwxrw- 1 root root    0 Mar 29 05:34 index.php
drwxrwxrw- 7 root root 4096 Mar 29 05:34 projects
-rwxrwxrw- 1 root root   25 Mar 29 05:34 robots.txt
drwxrwxrw- 2 root root 4096 Mar 29 05:35 tmp

Not that.
Those are an obvious hack (to me) to force it to work.

See http://askubuntu.com/questions/47521...ocal-webserver

What is your DocumentRoot set to?

wh33t · 03-31-2014, 04:06 PM

Quote:

Originally Posted by Habitual

Not that.
Those are an obvious hack (to me) to force it to work.

See http://askubuntu.com/questions/47521...ocal-webserver

What is your DocumentRoot set to?

Document root is set to /var/www

Habitual · 03-31-2014, 04:08 PM

Code:

grep -e apache -e www /etc/passwd

output?

Edit: does http://localhost/testphp.php work
from http://www.howtoforge.com/ubuntu_lamp_for_newbies ?

wh33t · 03-31-2014, 04:29 PM

Quote:

Originally Posted by Habitual

Code:

grep -e apache -e www /etc/passwd

output?

Edit: does http://localhost/testphp.php work
from http://www.howtoforge.com/ubuntu_lamp_for_newbies ?

Code:

root@xxxx:~# grep -e apache -e www /etc/passwd
www-data:x:33:33:www-data:/var/www:/bin/sh

This whole thing was running completely fine a day ago. I swear I woke up next morning and it started doing this to me.

Habitual · 04-01-2014, 08:32 AM

Quote:

Originally Posted by wh33t

Code:

root@xxxx:~# ls -l /var/www
-rwxrwxrw- 1 root root    0 Mar 29 05:34 index.php
drwxrwxrw- 7 root root 4096 Mar 29 05:34 projects
-rwxrwxrw- 1 root root   25 Mar 29 05:34 robots.txt
drwxrwxrw- 2 root root 4096 Mar 29 05:35 tmp

as root:

Code:

chown -R www-data:www-data /var/www

Restart apache|httpd, test. Report back.