Is this just a thing with me, or is the game down for everyone?
|-||Ryuzaki4Days||1m||Take drugs. Kill a bear.|
|-||Kiwi||5m||I guess there's always something killing me.|
|-||batko||4m||pussy like jamba juice|
|And 17 more hiding and/or disguised|
Sindome.org/characters, Log in via Play Now, you'll go through two screens.
There's sometimes a short lag while it loads but that could just be me.
Push the page reload button if it doesn't load.
You can also try via the Play Now option at the top of the Features page (co char name passie).
For some reason when I try to log in the 'Play As...' part for my char, the Connect button refuses to log me in to the MOO, doing nothing at all.
Reload does nothing, still a blank screen.
Feature's button as the play does the blank screen and/or refusing to connect to my char directly.
If this means I can't get my fix of SD and this persists, then that means I might have to stop playing SD. D:
Is this the same browser you were using back when this used to work for you or have you changed browsers since then?
Have you done things like quitting and restarting your browser? Clearing its cache? Trying a DIFFERENT browser?
Have you tried the "private", "anonymous" or "incognito" mode in whatever your browser of choice is? (ALL modern ones have this feature.)
Have you tried using the HTTPS instead of HTTP version of the webclient webpage? (Either click the "Lock" icon next to the webclient login form, or, just edit the address in the browser bar so it says https:// instead of http://)
Have you tried doing what we call a "hard refresh" on the screen where you're getting the blank? (Hold down the shift key while doing refresh with the browser's reload button, or, hold down the shift key while doing [ctrl]+[r])
While on the webclient login page, before clicking the "Connect" button, have you ever been presented with a browser warning about a security certificate? If so, did you choose to obey the warning or did you choose to instead proceed anyway despite the warning? (Hint: Do the second.)
When the server needs to have its webclient app restarted, the symptom is USUALLY different than this blank-black-screen problem (you usually see a white screen with a "too many open files" error in black text), and, it affects many people until it's resolved, not just one person persistently.
This is why I recommend trying as many things as we can think of to figure out what's going on on your end. Because, the webclient is fine for everyone else right now, and, there's nothing we can restart or poke in order to fix your problem for you. But, we can help you brainstorm.
See if any of this helps.