lighttpd 1.4.11 for Windows

PLEASE NOTE: Native Lighttpd Windows builds are available at http://en.wlmp-project.net/
The last available Lighttpd for Windows build that I created using Cygwin was Lighttpd for Windows 1.4.17.
Updated September 29, 2009.

Although the source has been available for a few days, lighttpd 1.4.11 for Windows is finally here. Besides the upstream fixes from lighttpd.net, a few minor changes exist in this release. The most major to note is that an alternative stop batch file is now available for XP (and up) users. It is called stop-lighttpd2.bat and can directly replace the regular stop batch file. As usual read the release notes (in the installer) before installing/upgrading. Regarding the new stop batch file, from the readme.txt:

stop-lighttpd2.bat is an alternate stop batch file for Windows XP which doesn’t need process.exe. It uses Windows’ taskkill.exe instead.

Download: lighttpd-1.4.11-win-setup.exe

If you download this version, please Digg it.. Thanks.

Post to Twitter Post to Delicious Post to Digg Post to Facebook Post to MySpace Post to Reddit Post to StumbleUpon

Did you enjoy this article? Please subscribe to my feed to receive all the FREE updates via RSS or Email - your choice!

{ 140 comments }

101 Kev June 28, 2006 at 08:43:05 AM

Michael, it may be available in the next version after 1.4.11.

102 Riobard July 10, 2006 at 11:00:47 AM

Kev,

I had cygwin and lighty for win installed on my XP machine previously. But after I uninstalled cygwin, lighty stopped working. I checked it with Task Manager, and found that when after start-lighttpd, the lighttpd.exe process appears in the task list and then exit.

Is there any thing wrong? I think lighty should work even without cygwin. Any suggestion?

103 Riobard July 10, 2006 at 11:00:47 AM

Kev,

I had cygwin and lighty for win installed on my XP machine previously. But after I uninstalled cygwin, lighty stopped working. I checked XP’s Task Manager, and found that when “start-lighttpd”, the lighttpd.exe process appears in the task list for a few seconds and then exit.

Is there any thing wrong? I think lighty should work even without cygwin. Any suggestion?

104 Riobard July 10, 2006 at 11:06:10 AM

sorry, the page stopped responding after my first post, so I simply retyped it once … not spam :)

105 Kev July 10, 2006 at 01:16:20 PM

Riobard: please look at this comment from above, and follow the same directions.

106 Riobard July 11, 2006 at 12:28:19 AM

Kev,

Yes I did do as the directions above before I made the post. I searched all cygwin1.dll on my system and deleted them. I even searched registry to remove anything related to it. Lighty doesn’t start up after I did all that. Any other idea?

107 Kev July 11, 2006 at 12:27:19 PM

Riobard: you deleted _ALL_ cygwin1.dll files from your system? You still need the one that is supplied with lighttpd, in the C:\lighttpd\sbin directory in order for lighttpd to work. Re-installing the package should work, make sure you make a bcakup first though.

108 Dey July 26, 2006 at 02:28:50 AM

Hi Kev,
Its been sometime and I have been running Lighty on a Windows 2000 server box for serving my php pages (wiki pages) in the intranet.
But I have observed a problem with pages either not loading quickly or completely stopped when I try and download some large files simultaneously.
Once I start the downloads of these files the entire site is crippled and no pages are served till the downloads are over.

Am not sure where the problems is. The files are hosted in a folder in the web root folder and they are indexed with a php script before being shown as links on a web page.

Can you help me with identifying the problem?
I checked the memory and CPU usage for Lighty and did not find anything out of place there.

The snapshot from the status page (which opens up after few minutes as the downloads are still on) is as below,
18350080/58425042 write 366 MVI_0235.AVI 18874368/55156046 write 385 MVI_0237.AVI 18874368/53570316 write 381 mvi_0236.avi

enabled: mod_access, mod_status, mod_cgi, mod_ssi, mod_accesslog

Thanks in advance.

109 Dey July 28, 2006 at 05:56:20 AM

Hi Kevin:I have been using lighty for sometime now to serve the wiki pages in my intranet. Lighty is running on a Windows 2000 box with 2GB RAM.
But I observed recently that while large files (video) are downloaded the site becomes slow and pages don’t get loaded until the downloads are complete or are extremely slow to come up in the browser.
Is there a way I can find out the problem? I enabled the server-status page and was not able to figure out the cause of this.
Any help is appreciated.
Thanks

110 De_Mon July 31, 2006 at 02:36:08 PM

1. Run InstSrv with following arguments: InstSrv lighttpd SrvAny.exe.

2. Run regedit and navigate to this key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lighttpd.

3. Create subkey ‘Parameters’.

4. Add ‘Application’ string value with exact fully qualified path:
‘C:\lighttpd\sbin\lighttpd.exe’.

5. Add ‘AppParameters’ string value with following data:
‘-f C:\lighttpd\etc\lighttpd.conf’.

6. Run the service using the standard Windows Services panel.

Hope this helps

111 huwnet July 31, 2006 at 03:15:10 PM

I am having a similar problem. I have been playing with cygwin recently. Everything worked fine while cygwin was installed (it even worked fine with cygwin in the path).

Now it is gone (and so have all the other cygwin1.dlls apart from the one bundled with lighty).

If I run lighty with -D everything works fine.

112 Igor August 2, 2006 at 01:31:01 PM

How come mod_webdav.dll is not present on the binary install?
lighttpd-1.4.11-win-setup.exe

C:\lighttpd\lib\
Does not contain the file on my install

on the list of files in the “installed binaries and support files” for the cygwin version the file is listed:
Sat Jan 21 10:48:18 2006 19456 usr/lib/lighttpd/mod_webdav.dll

113 Kev August 3, 2006 at 04:37:51 PM

Igor: If I recall correctly, webdav support was not compiled into this version.

114 Juansa August 4, 2006 at 03:30:27 PM

lighttpd for Windows doesn’t work when using the Comodo Personal Firewall….. why???

115 Kev August 5, 2006 at 01:15:40 PM

Juansa: the firewall is most likely blocking the port that lighttpd is listening on which is port 80 by default. Open up that port on the firewall and it should work.

116 Igor August 12, 2006 at 04:10:26 PM

Thank You Kev,
Do you know of a workaround or any way to make WebDav work under windows? any idea about supporting it on future. or how to get an older version of mod_webdav.dll file?
Thank you again. IL

117 Kev August 13, 2006 at 08:51:40 PM

Igor: It has to be compiled in, and so far it simply has not been. It may be available in the next version of lighttpd for windows.

118 Joe August 13, 2006 at 11:57:54 PM

Same problem as huwnet. I had cygwin installed a few months back but had uninstalled it. lighttpd doesn’t start using the startup script. However, adding the -D flag seems to allow it to start up.

119 Juansa August 17, 2006 at 01:30:30 AM

“Kev: the firewall is most likely blocking the port that lighttpd is listening on which is port 80 by default. Open up that port on the firewall and it should work.”

i dont think is that so… because the problem i has was something like “fatal
error – couldn’t release memory….mod_access.dll” even when i turned the firewall off (allow all) …and when i uninstalled the comodo lighttpd works just fine. but i need a firewall and comodo is the best free firewall i found.

thanks.

120 dan September 7, 2006 at 02:33:55 PM

OK, so I downloaded lighty and php and installed it successfully on my local winxp machine in under 5 mins. Great job ;)

Then I go to do it for real on a win2kpro (sp4) machine and i get some behavior similar to what a couple others have posted:

i start lighty and nothing happens. no errors, nothing in the task manager, nada. I’ve tried it with the default config and a few variations but am getting absolutely nowhere fast. from cmd, when i try the variations of the startup line detailed above, i press return and am immediately returned to a prompt

anyone solved their previous problems or have a new idea for me to try? i’ve doublechecked and the cygwin file i have is the one that comes with this lighty distro

thanks in advance

dan

121 Kev September 7, 2006 at 05:27:28 PM

dan: did you try adding the -D option to the start-lighttpd.bat file? It should say:
lighttpd.exe -f ..\etc\lighttpd.conf -D

Executing the above command from a command prompt (C:\>) in the C:\lighttpd\sbin\ directory can quickly verify this. If that is not the problem, other errors will also be displayed by using this method. Good luck, and let me know how it works out.

122 dan September 7, 2006 at 06:31:19 PM

ah thanks for the correct syntax for th -D option but still no joy… from the command line, lighttpd.exe -f ..\etc\lighttpd.conf -D simply returns me back to the prompt

i mean, i should definitely see lighttpd.exe in task manager if its startin correctly, right? thanks again for your assistance

dan

123 Kev September 7, 2006 at 08:27:23 PM

dan: yes, it should show up in the task manager. I’m not sure why this keeps returning you back to the prompt. If you have a firewall, disable it momentarily or be absolutely positive that port 80 is open and allowing traffic in and out.

124 dan September 7, 2006 at 08:53:33 PM

well, no firewall… tried ports 80, 81 and some high numbered ones in the 8000 range. ive got a SECOND win2kpro box, guess i’ll try it on there see if its consistent at all

thnx for the help, i’ll post back

dan

125 dan September 8, 2006 at 02:19:39 AM

ok, much better results on the second box (which is actually the intended target). i edited the default configuration to use port 8888, as this is a production web server, and doubleclicked the .bat file… it started, saw it in the task manager processes list

however, the firewall gave me what i thought was an odd message:

‘LIGHTTPD.EXE’ from your computer wants to send UDP datagram to foo.bar.com [127.0.0.1], port 3665

regardless, i said permit… and then it just seemed to loop from sending/receiving, with the firewall poppin up every 2 seconds. so i stopped lighty and tried it from the command line, and i received a similar message about a UDP datagram on a different 3000 range port

what exactly is goin on here and what ports do i need to open in order for this to run correctly?

thanks again

dan

Comments on this entry are closed.

{ 3 trackbacks }

Previous post:

Next post: