@Martin Kucej: It is impossible to fix this bug until its root cause is
known, see comments 13 and 14 for details. Please be patient.
** Tags added: maverick natty
** Tags removed: karmic
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
This bug still persists in 10.04.2. I can't be that hard to fix guys.
Can it?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/370542
Title:
Accessing http://localhost gives a 403 For
Still affected me on 10.04
nm:0.8-0ubuntu3
uname :Linux 2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:22:14 UTC 2010 i686
GNU/Linux
apache:2.2.14-5ubuntu8
I have encountered so many problems with the Network-Manager,Will Ubuntu switch
to wicd at any chance?
--
Accessing http://localhost gives a
** Tags added: jaunty karmic lucid
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
https://bugs.launchpad.net/bugs/370542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
The bug still exists in Ubuntu Lucid Lynx (10.04), with the exast same symptoms
amd solutions. At least in my case.
kernel: 2.6.32-23-generic
apache: 2.2.14-5ubuntu8, mpm-prefork
network-manager: 0.8-0ubuntu3
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost
Any news with alpha6 ?
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
https://bugs.launchpad.net/bugs/370542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in ubuntu.
--
Ubuntu
Has someone tried to reproduce this bug in Karmic Alpha2 ?
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
https://bugs.launchpad.net/bugs/370542
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscrib
@Jonathan: Yes, I agree that this is clearly related to the
NetworkManager. That said I'm not convinced that is an actual bug in
Network Manager. For example; compare to sshd, which doesn't have any
trouble with Network Manager and its ipv6 behavior.
Anyway, I'm changing the Status to Confirmed. W
OK. The underlying issue here now seems to be:
On Ubuntu 9.04 Desktop, Network Manager causes a network configuration
that leads Apache to start up listening on IPv6, but to restart
listening on IPv4. Specifying network configuration using
/etc/network/interfaces does not cause this behaviour, a
I observe exactly the same behaviour as Andreas did on his desktop
install, right down to everything being fine when I use
/etc/network/interfaces instead of NetworkManager.
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
https://bugs.launchpad.n
With "Allow from all"-option, http://[::1]/ , http://127.0.0.1/ and
http://localhost/ are all working. So this is a problem with "Allow from
localhost" or a specified ip address.
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
https://bugs.launch
@Andreas: Before editing /etc/apache2/sites-avaible/default the apache
was working normally (but I didn't check it after restart). I'm using
NetworkManager. I will now test the "Allow from all"-option.
As Martin said, http://127.0.0.1 is working.
** Attachment added: "hosts"
http://launchpadli
@Jonathan: You are right, I should test more and speculate less. I guess
I got a bit carried away. Thanks for pointing it out.
Regarding the part of listening on ipv6 I actually did some testing, on
a server install of 9.04. This is the result I got.
andr...@pc13267v1:~$ sudo netstat -ntlp | grep
@Andreas: When troubleshooting Ubuntu, please do not "think so", please
test instead :)
All my Intrepid Desktop VMs have "::1 ip6-localhost ip6-loopback", and
all my Jaunty VMs have "::1 localhost ip6-localhost ip6-loopback" in
/etc/hosts.
Further, both on Intrepid and on Jaunty, Apache2 *does* l
Hi!
Damn, you're fast... :)
I tried Jonathan's suggestions (A) and (B) as listed under EVIDENCE, and
each one resolved the issue.
Still, I think there's more to it than "IPv6 awareness" alone.
Otherwise, running "sudo /etc/init.d/apache2 restart" wouldn't change
anything, would it? By the way,
@papukaija: Just for confirmation; are your problems depending on "Allow
from localhost" or do they also occur using "Allow from all". How does
your /etc/hosts look like? Using the NetworkManager?
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
h
@Martin: Actually, failed to reproduce using your recipe. Sounds like
your last suspision might be right. Are you using NetworkManager? In
system och session mode? I'm not. Will have to get back to you when I
have a Jaunty system using NetworkManager, which I can reboot and test.
@Jonathan: Actual
** Summary changed:
- Accessing http://localhost gives without reason a 403 Forbidden error page
+ Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
--
Accessing http://localhost gives a 403 Forbidden when using apache "allow
localhost" directive
ht
18 matches
Mail list logo
