Just in case this helps, WebLab-Deusto is using several ports by default for the different components. You can see them in the "configuration.yml" file. In the default configuration, you'll have something like this:
Where there is a single host (core_host), with two processes (core_process1 and laboratory1); the former ("core") listening on 10000 and the latter has two components (the laboratory server "laboratory1" listening on port 10001 and the experiment server "experiment1"). Later, you'll have an Apache server or mapping <public-ip>:80/weblab/ to the port 10000, which is the ' core' server, who knows how to talk in the port 10001 with the laboratory server, who knows tha it can talk with the experiment server without a network since they're in the same process.
In you case, there seems to be an error with port 10001. If that port is a laboratory server, you should be able to open it like:
And in "index.html" you should see a file talking about "WebLab internal communications".
If you do not find any other log file, one trick that may help is installing 'tcpflow' in your Linux host (e.g., in Ubuntu it would be):
$ sudo apt-get install tcpflow
And then checking what's going on later:
$ sudo tcpflow -i lo -C port 10001
Which means: "read all the traffic in the localhost interface of whatever happens in port 10001". You may see an answer from other process (e.g., maybe your server is running other process and port 10001 was busy), or you see another error. If the server has another process, you can either change that process or change WebLab-Deusto ports by running:
$ weblab-admin create example --start-port=20000
Or manually changing configuration.yml AND debugging.py.