[Bug 551211] Re: can't bind to port 80

2013-01-23 Thread Stefan Bühler
This has been fixed upstream in 1.4.27, for details see http://redmine.lighttpd.net/projects/lighttpd/wiki/IPv6-Config The debian script can be used again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bug

[Bug 551211] Re: can't bind to port 80

2010-08-04 Thread Durand D'souza
It's still a problem in maverick. -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/

[Bug 551211] Re: can't bind to port 80

2010-05-13 Thread bodhi.zazen
This bug is still a "problem" in lucid. # service lighttpd start Syntax OK * Starting web server lighttpd 2010-05-13 20:37:27: (network.c.345) can't bind to port: :: 80 Address already in use # apt-cache show lighttpd Package: lighttpd

[Bug 551211] Re: can't bind to port 80

2010-04-05 Thread Andres Rodriguez
That's why the use-ipv6 script in lighttpd.conf is now disabled by default. As I previously said over a discussion on irc and as explained in the Debian bug, this will be addressed differently by upstream developers of lighttpd [1], for lighttpd sandbox/2.0. [1]: http://bugs.debian.org/cgi-bin/bug

[Bug 551211] Re: can't bind to port 80

2010-04-04 Thread RoyK
The proposed fix seems to break IPv6 after all, changing bind address to localhost instead of "any". -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Kenneth O'Brien
** Changed in: lighttpd (Ubuntu) Assignee: Kenneth O'Brien (kobrien) => (unassigned) -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Kenneth O'Brien
This fixes the issue. ** Attachment added: "Fixed bind issue without breaking ipv6" http://launchpadlibrarian.net/43008026/lighttpd_1.4.26-1.1ubuntu2.debdiff -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu B

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Launchpad Bug Tracker
This bug was fixed in the package lighttpd - 1.4.26-1.1ubuntu2 --- lighttpd (1.4.26-1.1ubuntu2) lucid; urgency=low * debian/lighttpd.conf: Comment 'use-ipv6.pl' by default, which causes failure to bind port in ipv4 (LP: #551211) -- Andres RodriguezSat, 03 Apr 2010 15:37:37

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Andres Rodriguez
According to comment [1] from upstream, they will have a new logic to handle IPV6 for lighttpd 2.0.x. They recommend to drop the use of use- ipv6.pl script by default. -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ub

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Andres Rodriguez
Hi all, You might want to commend in lighttpd.conf the following: include_shell "/usr/share/lighttpd/use-ipv6.pl" On the other hand, you might wan't to check [1]: [1]: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=560837 ** Bug watch added: Debian Bug tracker #560837 http://bugs.debian.o

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Kenneth O'Brien
*patching this* -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bu

[Bug 551211] Re: can't bind to port 80

2010-04-03 Thread Kenneth O'Brien
** Changed in: lighttpd (Ubuntu) Assignee: (unassigned) => Kenneth O'Brien (kobrien) -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu

[Bug 551211] Re: can't bind to port 80

2010-03-31 Thread Kenneth O'Brien
Doesn't start, no. -- can't bind to port 80 https://bugs.launchpad.net/bugs/551211 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu

[Bug 551211] Re: can't bind to port 80

2010-03-30 Thread Daniel Hahler
No, that's not related to spawn-fcgi. I can confirm that nothing is running on port 80 for me, too ("netstat -tulpen | grep 80"). Using port 81 in the lighttpd conf works however. @Kenneth: does lighty start for you on port 80? ** This bug is no longer a duplicate of bug 378772 [needs-packagi

[Bug 551211] Re: can't bind to port 80

2010-03-29 Thread Kenneth O'Brien
*** This bug is a duplicate of bug 378772 *** https://bugs.launchpad.net/bugs/378772 I assume a missing a dependency? ** This bug has been marked a duplicate of bug 378772 [needs-packaging] spawn-fcgi package needed for both cherokee and lighttpd -- can't bind to port 80 https://bugs.lau

[Bug 551211] Re: can't bind to port 80

2010-03-29 Thread Kenneth O'Brien
*** This bug is a duplicate of bug 378772 *** https://bugs.launchpad.net/bugs/378772 Output from me. (clean install lucid beta 1) * Starting web server lighttpd 2010-03-29 23:32:04: (network.c.345) can't bind to port: :: 80 Address already in use [fail] invoke-rc.d: initscript lighttpd, actio