search

matrix-org / matrix-appservice-discord

A bridge between Matrix and Discord.
Apache License 2.0
812 stars 152 forks source link

Error when using Docker container: 'User ID already taken' #721

Open hwittenborn opened 3 years ago

hwittenborn commented 3 years ago

I'm seeing this error, which appears to be causing everything to not work properly:

[bot-sdkMatrixLiteClient (REQ-1)] error: [ { errcode: 'M_USER_IN_USE', error: 'User ID already taken.' } ]

After this the container appears to just be quitting, and the bot doesn't do anything like join rooms.

d-513 commented 3 years ago

same error

Sorunome commented 3 years ago

Those should be safe to ignore. What are your "not working" symptoms?

hwittenborn commented 3 years ago

"Not working" is the following:

I'm not sure why, but attempting to run docker logs on the container is also mysteriously not showing anything now.

hwittenborn commented 3 years ago

Just turned on verbose logging, and it's outputting logs just fine again.

It's also saying that the bot started successfully now (don't know why the error's just gone now; I did change over to the develop image beforehand though), but the issue about the bot not joining rooms is still present.

hwittenborn commented 3 years ago

Went back to the latest image, but I'm still not getting any dice with it joining rooms (the original error's still gone though, so it's a step in the right direction anyway).

Synkstar commented 2 years ago

Im getting this same issue actually. Its just the bot doesnt join the matrix room when its invited but it shows up on discord as being online.

discordrelay_1 | Dec-7 13:15:54.636 [bot-sdkMatrixLiteClient (REQ-1)] error: [ { errcode: 'M_USER_IN_USE', error: 'User ID already taken.' } ] discordrelay_1 | PayloadTooLargeError: request entity too large discordrelay_1 | at readStream (/node_modules/raw-body/index.js:155:17) discordrelay_1 | at getRawBody (/node_modules/raw-body/index.js:108:12) discordrelay_1 | at read (/node_modules/body-parser/lib/read.js:77:3) discordrelay_1 | at jsonParser (/node_modules/body-parser/lib/types/json.js:135:5) discordrelay_1 | at Layer.handle [as handle_request] (/node_modules/matrix-bot-sdk/node_modules/express/lib/router/layer.js:95:5) discordrelay_1 | at trim_prefix (/node_modules/matrix-bot-sdk/node_modules/express/lib/router/index.js:317:13) discordrelay_1 | at /node_modules/matrix-bot-sdk/node_modules/express/lib/router/index.js:284:7 discordrelay_1 | at Function.process_params (/node_modules/matrix-bot-sdk/node_modules/express/lib/router/index.js:335:12) discordrelay_1 | at next (/node_modules/matrix-bot-sdk/node_modules/express/lib/router/index.js:275:10) discordrelay_1 | at expressInit (/node_modules/matrix-bot-sdk/node_modules/express/lib/middleware/init.js:40:5) discordrelay_1 | PayloadTooLargeError: request entity too large

Synkstar commented 2 years ago

I just fixed it. I had matrix.nasulex.net as the domain and thats what was causing the problem. The domain is supposed to be what it displays as so I had to put mine to nasulex.net because its delegated to that. But you still have to leave the homeserverurl as the direct link to the server which is matrix.nasulex.net in my case

hwittenborn commented 2 years ago

I wouldn't be able to confirm on my end if the issue still persists, as I've since stopped using Discord for the purposes I was using the bridge for and I can't really confirm if anything fixes it anymore.

I'll leave it up to y'all to decide what to do with this issue.

laur89 commented 2 years ago

Those should be safe to ignore. What are your "not working" symptoms?

Should it be logged as error then?

Wamy-Dev commented 1 year ago

any fix?