Kerika behind a firewall

Short-version: Kerika is supposed to let you connect to other users even if you are behind a firewall, but that isn't working right now: we have a bug that we want to hope in the next few weeks.

Long-version: normally your Kerika application would try to use ports 10421 and 10422 to connect to our rendezvous server, and thence to other Kerika users who are online. (First it would try port 10421, if that failed it would try port 10422).

If neither port is open, e.g. because you are behind a corporate firewall, your Kerika application is supposed to use port 80 -- which is almost always open since this is the port that your browser uses to access the Internet -- to connect to a relay server at our data center. The relay server is then supposed to then act as an intermediary between you and the storage server and other Kerika users who happen to be online.

But there's a bug. Right now the relay server settings, at the data center and on your computer, are also trying to use the same ports 10421 and 10422, instead of using port 80. Which means that if your firewall is already blocking these ports, the relay server won't work either!

The fix to this problem isn't very hard, but unfortunately now is not a good time for us to implement it because we are deep in the process of wrapping up our next version, which is going to have some very significant improvements and new features. We will try to make sure the fix goes into this version, but there is a lot of testing still left to do so we won't be able to roll out the fix for a few weeks at least.

Our sincere apologies for hassles created by this bug...