-
Notifications
You must be signed in to change notification settings - Fork 616
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
Whatsapp bridging stopped working: Client outdated #2146
Comments
I have the same problem, it seems to be a problem with the following module: |
In that topic they discuss login problems with the QR-code, but matterbridge stops even before showing a QR-code. I don't know but it is probably just a matter of the whatsmeow version (and therefore the web version) being too old. After the bridge stopped working this night, i built a new one this morning, but that is still exactly the same as the one that was running since september 2023. So it's not unlikely for the used whatsmeow version to be outdated. @42wim, is it possible for you to update the whatsmeow version for the self-build process? |
Same here... |
@tzagim :
So can you please update to the latest Go module as well? |
Same here ☝🏽 |
Try now |
For me it compiled ok: root@sede-automations:~/go/bin# CGO_ENABLED=0 go install -tags whatsappmulti github.com/tzagim/matterbridge@master But when running i get this error: [0000] INFO router: Starting bridge: whatsapp.mywhatsapp Something about this: I'm not really a coder, so can't help too much. |
Compiled OK here as well. I can confirm what @rasysdev already reported and got the same errors:
So it's more complicated... |
Really need this wpp bridge to work, so i asked a developer i know to fix it: |
Nice! But did you build it before 3b31b54 ? Because when trying to build it, it will give this error:
|
@Vetgans
You will get the same error (#2146 (comment)). |
I can confirm this... @rasysdev: |
git clone https://github.com/rodrigozietlow/matterbridge.git then i went in /root/go/bin and the "mattermost" there worked. Maybe some URLs need to be changed to compile in the normal way... But i did this way and is still running. Edit: I cloned from the branch master. |
Building from master gives me the following error:
Understandable, as @rodrigozietlow made commit 3b31b54 for the Pull request. Building without that last commit by using Running that file however still throws the error that it fails to connect to the database:
I've done everything all over again, but still the same errors. Is it perhaps possible for you to upload the resulting file? |
Did you build id with ./ ? What resulting file are you refering to? The "mattermost" file from go bin? |
Yep
The resulting matterbridge file |
See the history: 353 cd /tmp/ The "matterbridge" file isn't it a binary? Can you debug by the binary? In that case i will somehow send it here. |
have you tryed deleting the old database file? |
What didn't worked was just using the go install command and just replacing the url like this: The issue is, that the URL is also referenced in other files. But the instructions of @rasysdev worked well:
Then you will have a new matterbridge executable in the ~/go/bin/matterbridge folder that works again until the pull request is merged. |
@rasysdev In my commands, I removed msteams and zulip. Maybe this could also work for you? But after I reinstalled the fork and used a new database, I still get an error after logging in:
So I think I have to wait for a few errors, because I'm not able to resolve that. |
These steps worked perfectly. Thank you @pegelf |
I started from scratch on another machine, and finally got it running. Still some errors are being reported:
Apart from that it seems to be running fine. |
I can confirm that this works. Thanks ! |
Everything still working fine. I did get these errors later last night
but it continued to run. Later last night i restarted with the session file, and ever since the bridge has been running well without any errors. Thanks to everyone who helped out, and in particular of course @rodrigozietlow for the vital commits. |
Describe the bug
Bridge has been running succesfully for months and months
Whatsapp bridging stopped working last night with log message that the client is outdated
To Reproduce
Steps to reproduce the behavior:
Build latest development version with
go install -tags nomsteams,nozulip,whatsappmulti github.com/42wim/matterbridge@master
Start the bridge. It will fail. The message of the client being outdated will appear.
Expected behavior
The bridge running succesfully like before
Screenshots/debug logs
The text was updated successfully, but these errors were encountered: