Which browsers are working currently?

[ez4u]

Currently I can not connect on Windows 7 using Firefox (15.0.1), Chrome (22.0.1229.94 m), or IE (9.0.10). I keep getting the little box that says I logged in successfully but the server can't reach me. So what is working for others?

[Bonobo]

Just connected OK. There seems to have been a problem with a full hard drive @ Kaya, quite a few people write in the chat that they had the same probs, and Gabriel aka conanbatt wrote about the HD problem and that it’s been repaired. Just try again.

For the record: OS X 10.7.5, Chrome (latest) and Safari (ditto) OK.

Greetings, Tom

[ez4u]

Thanks, that seemed to work, i.e. the box disappeared. However, it turns out that I can not do anything. All attempts to post a chat return "Your Session has timed out. Log back in". Attempting to create a sandbox produces a "file not found:" message after the server attempts to kick me back to "https://beta.kaya.gs/You%20don't%20have%20a%20session.%20Log%20in%20or%20create%20an%20account."

[Kaya.gs]

Thanks, that seemed to work, i.e. the box disappeared. However, it turns out that I can not do anything. All attempts to post a chat return "Your Session has timed out. Log back in". Attempting to create a sandbox produces a "file not found:" message after the server attempts to kick me back to "https://beta.kaya.gs/You%20don't%20have%20a%20session.%20Log%20in%20or%20create%20an%20account."

If you havent refreshed, logged in since release, you will have to do it again, as we made a small change in the session management.

If problem persist, tell me on the support channel.

[ez4u]

Thanks, that seemed to work, i.e. the box disappeared. However, it turns out that I can not do anything. All attempts to post a chat return "Your Session has timed out. Log back in". Attempting to create a sandbox produces a "file not found:" message after the server attempts to kick me back to "https://beta.kaya.gs/You%20don't%20have%20a%20session.%20Log%20in%20or%20create%20an%20account."

If you havent refreshed, logged in since release, you will have to do it again, as we made a small change in the session management.

If problem persist, tell me on the support channel.

That did it!