If you are unable to log in through the web-interface to your sBNC account this is the 4 most likely causes you need to check. The steps in this guide is for sBNC 1.1 only (not 1.2).

For sBNC to be able to understand and talk with the web-interface, it needs to understand TCL. This is possible through the file tickle.so, which is the TCL module.

First check if you have the module loaded. While logged in to your sBNC account over IRC, use the following command:

/sbnc lsmod

If there is a line with “tickle.so” in it, you have the module loaded, and you can move on to the next check. If not, here is how you first get it compiled and then loaded.

1. Connect to your server through SSH with a client like PuTTy.
2. Go to the “tickle” folder in the sBNC 1.1 source code folder, usually ”~/sbnc-1.1/tickle”:

   cd ~/sbnc-1.1/tickle

3. Check if all the dependencies are there:

   ./configure

   • If output of the command above had some errors regarding about files and TCL in general, it is because your server does not have the “tcl8.4” and “tcl8.4-dev” packages installed, which the TCL module relies on. If you have root access, installed them through your OS' package manager or library. See Installing TCL for details.
4. After you have run the command above successfully, it is time to compile and install the module using the following command(s):

   make && make install

   • The first “make” will compile the module, and the second “make install” will copy it to the appropriate folder.
   • If successful, it tells you what to do next. Something about using the sBNC command “insmod” to load the module.

While the TCL module, we made sure were loaded above, makes sBNC understand the TCL language, the actual instructions that make sBNC able to communicate with the web-interface is in “scripts/iface.tcl”.

1. Open up the file ”~/sbnc/sbnc.tcl” in your favorite editor, and check if it contains the following line:

   source "scripts/iface.tcl"

   • If it does you can move on to the next check.
2. Add code above to the ”~/sbnc/sbnc.tcl” file.
3. Rehash your TCL module, making it reload all it's .tcl files. Command is to executed in your IRC client while connected to sBNC:

   /sbnc tcl rehash

   • It will return something like ”<null>”.

When sBNC's TCL module reads “iface.tcl” it creates a TCP listener on a port defined in “iface.tcl”. The web-interface' “config.php” has a setting telling it what port it should attempt to find the listening TCL script on. It is vital that this port is not being used for anything else. It can't even be the port sBNC uses for connecting users.

The default port is 8090.

• In “iface.tcl” the line defining the setting will look like this:

  set ::ifaceport 8090

• In “config.php” the line(s) defining the setting will look like this:

  $connections = array(
      "sBNC" => "127.0.0.1 8090"
  );

  • If you are running the web-interface on another server/machine than sBNC is running on. You can specify the IP it should be connecting to in the same line.

Check that you are in fact using the proper username/password combination. Look at character cases, and so on.