Project

General

Profile

Bug #1469

Always get "default document-root has to be set" error

Added by Anonymous almost 12 years ago. Updated almost 11 years ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
core
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

I've got lighttpd-1.4.18 compiled --with-openssl
Running as root (just for testing) with this config:

$SERVERsocket == "127.0.0.1:443" {
ssl.engine = "enable"
ssl.pemfile = "/private/127.0.0.1.pem"
server.name = "127.0.0.1"
server.document-root = "/web"
}

always fails with the error:

a default document-root has to be set
setting default values failed

I've tried changing the config in many ways, but the same error always appears.
There seems to be a total lack of useful debugging info. Running with -t gives
no useful info (no syntax errors). Running with -p is unhelpful (just the internally
parsed version of the config file).

I'd really appreciate any ideas on how to get this thing running.
Thanks.

History

#1

Updated by Anonymous almost 12 years ago

I've got lighttpd-1.4.18 compiled --with-openssl

Running as root (just for testing) with this config:

(how do you get brackets without links in this wikimarkup?)

'''$SERVER'''<nowiki>(open square bracket)'''"socket"'''(close square bracket)</nowiki> '''== "127.0.0.1:443" {'''
'''ssl.engine = "enable"'''

'''ssl.pemfile                 = "/private/127.0.0.1.pem"'''
'''server.name                 = "127.0.0.1"'''
'''server.document-root        = "/web"'''
'''}'''

always fails with the error:

a default document-root has to be set
setting default values failed

I've tried changing the config in many ways, but the same error always appears.
There seems to be a total lack of useful debugging info. Running with -t gives
no useful info (no syntax errors). Running with -p is unhelpful (just the internally
parsed version of the config file).

I'd really appreciate any ideas on how to get this thing running.
Thanks.

#2

Updated by darix almost 12 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

server.port = 443
ssl.engine = "enable" 
ssl.pemfile = "/private/127.0.0.1.pem" 
server.name = "127.0.0.1" 
server.document-root = "/web" 

this is a bug tracker not a support tool. the error message was correct as you did not configure a document root in the global scope, but to achieve a ssl only server see the config snippet above.

#3

Updated by Anonymous almost 12 years ago

  • Status changed from Fixed to Need Feedback
  • Resolution deleted (invalid)

Ok, thanks for the tip. As I was using the "links" browser (without CSS), I didn't see the notice that this is not a support tracker. Sorry about that.

By the way, do you have a feature requests tracker too?

I'd like to log a suggestion that the error message when document root is set within local scope should be expanded to explain the cause in more detail, i.e. "have you set a document-root within the global scope (outside any SERVER sections)?"

Thanks.

#4

Updated by admin almost 12 years ago

This tracker accepts feature requests (type: enhancement).

#5

Updated by stbuehler over 11 years ago

  • Status changed from Need Feedback to Fixed
  • Resolution set to invalid

There will be never a good enough documentation, but feel free to improve it.

I really think the error message is pretty clear if you understood how the config works, and i think that is the real problem as lightys config is a little bit unusual (i think i learned most things about the config while i was reading the source ;-) )

But still this is no bug itself.

#6

Updated by stbuehler almost 11 years ago

  • Status changed from Fixed to Invalid

Also available in: Atom