[mod_onions] Top Level error when loaded before mod_s2s

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download and enable mod_onions module on 0.9.7 on FreeBSD 10
2. At prosody start-up check prosody.err error file
3. The error will be seen

What is the expected output? What do you see instead?
Expected output is successful loading of mod_onions.
Output is instead:

Feb 24 20:49:38 general error   Top-level error, please report:
/usr/local/lib/prosody/modules/mod_onions.lua:76: attempt to index a nil value
Feb 24 20:49:38 general error
stack traceback:
        /usr/local/lib/prosody/modules/mod_onions.lua:76: in function 'socks5_handler'
        /usr/local/lib/prosody/modules/mod_onions.lua:173: in function 'readbuffer'
        /usr/local/lib/prosody/net/server_select.lua:854: in function </usr/local/lib/prosody/net/server_select.lua:836>
        [C]: in function 'xpcall'
        /usr/local/lib/prosody/../../bin/prosody:376: in function 'loop'
        /usr/local/lib/prosody/../../bin/prosody:407: in main chunk
        [C]: at 0x00404840

What version of the product are you using? On what operating system?
Prosody 0.9.7 with luajit from ports on FreeBSD 10

Please provide any additional information below.
mod_onions downloaded from https://code.google.com/p/prosody-modules/

Original issue reported on code.google.com by b.manas...@gmail.com on 24 Feb 2015 at 8:53

[GoogleCodeExporter]

Sorry, please ignore.
The configuration required modules_enabled = { "onions" }; in the VirtualHost 
section and not in the global modules section.

Original comment by b.manas...@gmail.com on 24 Feb 2015 at 9:08

[GoogleCodeExporter]

Hi, thanks for the report!

This actually is a bug, though I think most people only load mod_onions on a 
single host so it hasn't been noticed before. I've fixed it in prosody-modules 
commit e0d8caffa209.

Original comment by MWild1 on 25 Feb 2015 at 5:29

• Changed title: [mod_onions] Top Level error when loaded before mod_s2s
• Changed state: Fixed