For the record, I've found out what the problem was. My test machines are behind a firewall and I was accessing the faban web page by forwarding the 9980 port through ssh. The whole problem resided in that I was redirecting my local port 1234 (the one I use in the browser) to faban's 9980, which made it fail (somehow, faban tried to connect to that port on its own machine). Forwarding my local port 9980 to faban's 9980 solved the issue.
Lluis Lluís Vilanova writes: > Cansu Kaynak writes: >> Since I've never run into this problem, the best I can suggest is to kill all >> the client processes you mentioned and start them again. > I even tried to reboot the machine to start fresh, but with no luck. > Any hints on how to debug what might be going on? -- "And it's much the same thing with knowledge, for whenever you learn something new, the whole world becomes that much richer." -- The Princess of Pure Reason, as told by Norton Juster in The Phantom Tollbooth
