Existing players used to logging in with their character name and moo password must signup for a website account.
- BlackSoul 31s
- Burgerwolf 10m PANCAKES
- MrRedgrave 1m
- Hivemind 20m
- SmokePotion 30s Right or wrong, I'm getting high.
- zxq 6m Tools: https://ansicolortool.neocities.org
- Rillem 3m Make it personal.
- Raven 1h I lost myself, in the dark charade.
- PsycoticCone 50m
a Butako 57m https://i.imgur.com/GsU4a79.jpg
a Mench 3h Doing a bit of everything.
- Wulf 22m
- Pladdicus 57s uh
- Vanashis 23m
- AntiqueBeast 20m
- whatislove 58m get big
- Euclid 1m
- Yizhi 3m
And 29 more hiding and/or disguised
Sindomedome logo
a cyberpunk roleplaying game
banner art by Grand Failure
Connect to Sindome @ moo.sindome.org:5555 or just Play Now

Login Issues

Login to post. Membership required.
Jump To
Newest Post
At first I couldn't log in and got the following response:

Error: EMFILE, too many open files '/home/ubuntu/dome-client.js/views/client.ejs'

at Object.fs.openSync (fs.js:439:18)

at Object.fs.readFileSync (fs.js:290:15)

at Object.exports.renderFile (/home/ubuntu/dome-client.js/node_modules/ejs-locals/node_modules/ejs/lib/ejs.js:273:12)

at View.module.exports [as engine] (/home/ubuntu/dome-client.js/node_modules/ejs-locals/index.js:86:7)

at View.render (/home/ubuntu/dome-client.js/node_modules/express/lib/view.js:75:8)

at Function.app.render (/home/ubuntu/dome-client.js/node_modules/express/lib/application.js:503:10)

at ServerResponse.res.render (/home/ubuntu/dome-client.js/node_modules/express/lib/response.js:718:7)

at exports.client (/home/ubuntu/dome-client.js/routes/screens.js:33:7)

at callbacks (/home/ubuntu/dome-client.js/node_modules/express/lib/router/index.js:162:11)

at param (/home/ubuntu/dome-client.js/node_modules/express/lib/router/index.js:136:11)

Now I'm able to log in, but I'm getting a black screen. This is on the web client.

By Crooknose at Jul 21, 2019, 7:06 PM | 0
I went out and back in again and the login worked. Weird. I did notice to autopruner running about 5-10 minutes before this.
By Crooknose at Jul 21, 2019, 7:07 PM | 0
The* autopruner
By Crooknose at Jul 21, 2019, 7:07 PM | 0
This happened to me when Crooknose posted this, and it just happened again. I went to check the boards for anyone else having an issue, then refreshed and was able to log in OK.

Another user in xgame said they had the same thing happen earlier. Just wanted to log this issue.

By ExMachinae at Aug 4, 2019, 8:16 PM | 0
I had this yesterday too, maybe around 7 pm PST, for like half an hour intermittently?
By KitchenSink at Aug 5, 2019, 7:32 AM | 0
Yeah, this happens with the webclient because of sockets being files and each connection to the MOO being a socket and some of them not closing properly. We have a scheduled job to restart the webclient run each week– but we've been talking about raising it to twice a week so combat this.

I had hoped upgraded socket.io to a newer stable version would help but it has not.

By Slither at Aug 10, 2019, 7:42 AM | 0
Anyone else having issues with login? Got booted and now it says problem loading page.
By Jade1202 at Aug 18, 2019, 10:46 AM | 0
Yeah emfiles are going wack. It's just the web client, though. Connecting through other clients are fine.
By NyanChicken at Aug 18, 2019, 10:50 AM | 0
Pls come back soon, webclient!
By NyanChicken at Aug 18, 2019, 11:01 AM | 0
How do we connect via a client? I'm gonna go download Mushclient I guess? What client do you guys use?
By JMo at Aug 18, 2019, 1:07 PM | 0
Found the info from an old post:

"[ INFO ] - Trying secure connection to moo.sindome.org: 5555 …"

By JMo at Aug 18, 2019, 1:14 PM | 0
Jump To Oldest Post