search

hifi / heisenbridge

a bouncer-style Matrix IRC bridge
MIT License
244 stars 34 forks source link

Existing channel memberships are working, but bridge user no longer responds to commands #280

Open kelnos opened 7 months ago

kelnos commented 7 months ago

Maybe similar to #278, but I don't see the errors in the status output that the reporter over there saw.

I set up heisenbridge... last fall? Or something. Version 1.14.5 at the time, but I've since updated to 1.14.6, using the docker container (hif1/heisenbridge:1.14.6). It worked fine, and I've connected to LiberaChat and OFTC with a few channels on each. Everything continues to work fine in those channels, I see others' messages, and others see my messages. But the @heisenbridge user on my homeserver no longer responds to any commands. I tried an /unignore like worked for the reporter in #278, but no luck.

Looking at history for the chat, looks like I set it up on Sept 1, 2023, and the next time I tried to issue it a command was on Sept 22, but it did not respond. I must have not thought anything of it at the time, but I've just gone back to it now, and it's still not responding.

systemctl status shows nothing interesting after a restart:

systemd[1]: Started heisenbridge.service - Heisenbridge Matrix->IRC Bridge.
docker[24487]: Heisenbridge v0.0.0
docker[24487]: Trying to detect homeserver public endpoint, this might take a while...
docker[24487]: Fetching joined rooms...
docker[24487]: Homeserver is publicly available at https://[redacted]
docker[24487]: Bridge is in 7 rooms, initializing them...
docker[24487]: All valid rooms initialized, connecting network rooms...
docker[24487]: Init done with 2 networks connecting, bridge is now running!

I tried enabling debug logging (adding -v -v to the startup script), and it does spew a lot of messages about the IRC connections. But when I send VERSION to the @heisenbridge account, nothing new is printed to the log. Anything else I can do to debug this?

kelnos commented 7 months ago

Also noticed that Element is showing that my message was sent, but has not been received/seen by the heisenbridge user.

bjo81 commented 7 months ago

I'm having the same issue - and I forgot what I did the last time when it happened.

NovaAndrom3da commented 6 months ago

I wonder if anyone has found a fix to this?

drscream commented 1 week ago

I've the same issue at the moment and looking for solution.

I've used Cinny to make a direct message to heisenbridge but this does not work. I would say the bot receive the message but doesn't answer. I've switched to Element (web application) and used:

Wrote "help" as the initial message and it worked! I expect it has something todo how the initial message is made by the client - or which type of message it is at the end.

kelnos commented 5 days ago

I just updated my synapse version to 1.118 (I was on a fairly old 1.91) and heisenbridge to 1.15.0 (from 1.14.6), and the problem seems to have resolved itself. Not sure which upgrade was responsible.

The client in use seems not to have mattered to me; I was using Element (web) and nheko when it didn't work, and now still nheko when it works.