Results 1 to 10 of 10
  1.    #1  
    I'm sure I'm missing something, but I can't figure out what.

    A while back I installed Lighty to browse local HTML on my Pre. I loaded stuff in a directory called .Various_HTML on /media/internal, and it worked great.

    At some point in the past three or four weeks, it just stopped working. Not even localhost will resolve, must less anything in .Various_HTML. I get:

    Code:
    Unable To Load Page
    http://localhost/
    Error loading page. [111]
    I have the latest Lighty update, and I know that things were moved to /media/internal/www, but I don't really know how that will or has affected things. I tried moving the .Various_HTML folder into /www, but it hasn't helped. I've rebooted my Pre (several times).

    I just can't figure out what has changed or how to fix it. I've scanned the extant Lighty threads, but couldn't find a fix. I'd really, really like to be able to access local HTML on my Pre again.

    Help?
    Jeff Wilder, San Francisco Bay Area
    "I think I speak for everyone here when I say, 'Huh?'" - Buffy Summers

  2.    #2  
    Nobody?
    Jeff Wilder, San Francisco Bay Area
    "I think I speak for everyone here when I say, 'Huh?'" - Buffy Summers

  3. #3  
    You can't access localhost with the webos browser.
  4.    #4  
    Quote Originally Posted by debilater View Post
    You can't access localhost with the webos browser.
    That's not correct. Using the lighttp (Lighty) web server, you can access localhost. (Or, at least, you could ... and I did. My inability to do so now is the whole point of my original post.)
    Jeff Wilder, San Francisco Bay Area
    "I think I speak for everyone here when I say, 'Huh?'" - Buffy Summers

  5. #5  
    I installed Lighty Web Server from Preware, and recently updated. I can still see my files. The version I have installed seems to be 1.4.25-6. Do you have other optware installed? It ought to be no problem, but, try process of elimination to see it if your localhost comes back.

    Also see if the pcre library and Optware Bootstrap is also on your Pre. They seem to be necessary for Lighty.

    I'd also recommend using Preware for install and removal of OptWare packages.
    Last edited by sethron; 03/29/2010 at 03:05 PM. Reason: check preware install list
  6.    #6  
    I uninstalled Lighty, rebooted, reinstalled Lighty, rebooted, deleted my local bookmarks, recreated my local bookmarks, and tried again. Everything works. No idea what in that process fixed things.
    Jeff Wilder, San Francisco Bay Area
    "I think I speak for everyone here when I say, 'Huh?'" - Buffy Summers

  7. #7  
    I just removed and reinstalled Lighty as well because it threw error 111. It's back up now. Do you have Save/Restore installed? That's the only diff I think of.
  8. #8  
    I can't get lighttpd running on Pre or Touchpad. I've had it running on both in the past, but use it infrequently, so I'm not sure when it 'broke' for me. When it has stopped working in the past on the Pre I would first go to Terminal and do a 'start mobi.optware.lighttpd' and if that didn't work, one or more re-installs through Preware. This time it isn't working... In Terminal (Pre) and xterm (TP) it looks like everything is fine, and no errors, but I still can't hit localhost. I decided to try wTerm on the pad and it gives me '-sh: start not found' so I thought I'd see what was in the mobi.optware.lighttpd event.d file for clues and found 'exec /opt/sbin/lighttpd -D -f /opt/etc/lighttpd/lighttpd.conf' so I tried that in wTerm and got an error about the shared library 'libpcre.so.0' being missing and saw that the version I keep re-installing seems to be 'libpcre.so.1.0.1' and I don't find where 'libpcre.so.0' gets specified so I can change it to use the current version. Can anyone provide help before I head to the doctor?
  9. #9  
    SOLVED:
    I don't know the whys, but I had to make new libpcre.so.0s.
    On the Touchpad I had only libpcre.so.1.0.1 so I did 'cp /opt/lib/libpcre.so.1.0.1 /opt/lib/libpcre.so.0' on the Pre I had 4 (!?): libpcre.so, libpcre.so.0, libpcre.so.0.0.1 and libpcre.so.1.0.1 BUT libpcre.so.0 and libpcre.so.0.0.1 were 0bytes so I did the same on the Pre and now I've got lighty running again on both.
    Anybody have an idea why I'd have these wacked-out extra libpcres?
  10. #10  
    Yes, updating the sym link solved the issue for me, too. rwhitby commented about this in github.

Posting Permissions