Trying to get to Wolfery I get :
An error occured when trying to authenticate:
Failed to connect to the realm.
If I use a private browser window I do get the login prompt but it fails with ‘Not Found’. Clearing my cache didn’t help.
Try again now!
I… erm… I tried to do things. I did things slightly wrong. 
There’s some other wrongness going on right now but it’s… subtle.
I get redirected to mucklet’s home page when I log in. There’s someone else who when they log in isn’t getting in properly.
I’m getting “Internal error: missing token” when I try to log in to the MUCK. When I enter a deliberately incorrect password, I get “Wrong password”, so it isn’t that.
Yeah… Things are a bit bumpy at the moment.
I am trying to work on that redirect issue at the moment. Sorry! 
Missing token is a cookie issue. And many of the things being problematic right now is due to cookies. Hopefully this one will also be sorted out very soon as well. Working on it!
Really? This is odd indeed. I am trying to troubleshoot at the moment.
But it is really odd.
It is strange. Why would just you get this? The error means simply that; the client failed to make a WebSocket connection to the api.
It might be some CORS issue again that has been activated due to a recent upgrade of the browser:
Which OS, and which Browser (including version) do you use?
And, if you go into Dev Tools (F12) and check the Networks tab, can you see what error you get from the api.wolfery.com websocket connection?
I am having very similar difficulties this eve (it is long since I last tried to log in). The actual message follows:
“Internal error: oauth2: cannot fetch token: 400 Bad Request
Response: {“error”:“invalid_request”,“error_description”:“The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed”}”
do you have any extension that tries to remove ads and such? Apparently they can get over-zealous. You can try a different browser and see if it works there.
That is slightly different error than “Failed to connect”.
But it is the exact same error as discussed in this thread:
I am still a bit stumped on the reason, and need more info. If you reply to some of my questions in that thread, it would help a lot!