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

Can't re/set admin room #971

Open
RoiArthurB opened this issue Sep 16, 2024 · 0 comments
Open

Can't re/set admin room #971

RoiArthurB opened this issue Sep 16, 2024 · 0 comments

Comments

@RoiArthurB
Copy link
Contributor

Issue

Pretty much as the title says.

I stupidly left my HS's admin room and I can't join it again. So I looked at the documentation and issues here and found a pretty similar issue: #579

So, as recommended by AndrewFerr in it, I removed the room, added back the bot in a new conversation, rebooted the server entirely; but it doesn't fix it and doesn't display any error in the logs anymore...

$ journalctl -fu matrix-hookshot
Sep 16 19:13:50 DietPi systemd[1]: Starting matrix-hookshot.service - A bridge between Matrix and multiple project management services, such as GitHub, GitLab and JIRA....
Sep 16 19:13:50 DietPi matrix-hookshot[66365]: Error response from daemon: No such container: matrix-hookshot
Sep 16 19:13:50 DietPi matrix-hookshot[66398]: Error response from daemon: No such container: matrix-hookshot
Sep 16 19:13:50 DietPi matrix-hookshot[66416]: 6513d71b9d74a04db855fedaed8649e26b997432698e01fde43ee53526b9d0ae
Sep 16 19:13:51 DietPi systemd[1]: Started matrix-hookshot.service - A bridge between Matrix and multiple project management services, such as GitHub, GitLab and JIRA..
Sep 16 19:13:56 DietPi matrix-hookshot[66469]: INFO 12:13:56:301 [ListenerService] Listening on http://0.0.0.0:9000 for webhooks
Sep 16 19:13:56 DietPi matrix-hookshot[66469]: INFO 12:13:56:308 [ListenerService] Listening on http://0.0.0.0:9003 for widgets

The only command working is the general !hookshot help but nothing else (see screenshot below).

image


How can I fix this issue ? Namely, found a way to either fully reset the bot, or more simply set a new admin room address to be able to administrate it.

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

1 participant