Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@heisenbridge user not available on Conduit.rs #134

Closed
poVoq opened this issue Jul 17, 2021 · 10 comments
Closed

@heisenbridge user not available on Conduit.rs #134

poVoq opened this issue Jul 17, 2021 · 10 comments

Comments

@poVoq
Copy link

poVoq commented Jul 17, 2021

Hello

am trying to get this to work with the Conduit.rs homeserver.

On the conduit side everything seems to be working and I added the content of the heisenbridge.yaml as described in the Conduit docu:
https://gitlab.com/famedly/conduit/-/blob/master/APPSERVICES.md

But when I start heisenbridge (connecting to http://localhost:6167 which is where Conduit runs) I just get the message about the version and the domain of my homeserver, but I can't start a DM with the @heisenbridge:myhomeserverdomain user.

It just says that the user is invited to the room...

As I am pretty new to this Matrix thing, I might be overlooking something, but it seems this might be a bug either in Heisenbridge or Conduit?

@namazso
Copy link

namazso commented Jul 17, 2021

considering conduit's development state i'd say its much more likely that they have a but and not heisenbridge

@hifi
Copy link
Owner

hifi commented Jul 17, 2021

Try starting with -vvv to get full debug output. I fixed some Conduit compatibility things before and Conduit also got some fixes so it should currently work unless something got broken again.

@poVoq
Copy link
Author

poVoq commented Jul 17, 2021

This is the debug output I get:

DEBUG:asyncio:Using selector: EpollSelector
Heisenbridge v0.99.2
DEBUG:root:Appservice user is already registered.
INFO:root:We are @heisenbridge:mydomain.com
DEBUG:root:Default config: {'networks': {}, 'owner': None, 'allow': {}}
INFO:root:Seems we are not connected to Synapse, inviting puppets is required.
DEBUG:root:Did not find .well-known for HS
Homeserver is publicly available at https://mydomain.com
INFO:root:Starting presence loop
DEBUG:root:Merged configuration from HS: {'networks': {}, 'owner': None, 'allow': {}}
DEBUG:root:Appservice rooms: []
INFO:root:Connecting network rooms...
INFO:root:Init done, bridge is now running!

Looks like the "inviting puppets is required" might be the issue?

@hifi
Copy link
Owner

hifi commented Jul 17, 2021

It's normal for it to say that about invites even on synapse. What does it say when you invite the bot with full debug output?

@poVoq
Copy link
Author

poVoq commented Jul 17, 2021

Ok after some joint bugfixing it seems the heisenbridge.yaml that gets imported into condit as an appservice needs another
- regex: '@heisenbridge'
in the users section, but the file loaded by heisenbridge itself should not have this modification.

@hifi
Copy link
Owner

hifi commented Jul 18, 2021

https://gitlab.com/famedly/conduit/-/issues/110

@hifi
Copy link
Owner

hifi commented Jul 22, 2021

@poVoq what version of Conduit did you use? The developer commented it should work.

@poVoq
Copy link
Author

poVoq commented Jul 22, 2021

I used the nightly version from 6 days ago. For now I have put this on the back-log as I am focusing on something else, but I plan to get back to it maybe next month.

@hifi
Copy link
Owner

hifi commented Jul 26, 2021

I confirmed this is an issue with Conduit.

@poVoq poVoq closed this as completed Jan 22, 2022
@poVoq
Copy link
Author

poVoq commented Jan 22, 2022

This is resolved with the conduit-next version I tried just now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants