#1888 mod_unified_push creates a looping reconnecting /announcing with mollysocket
Reporter
Menel
Owner
Nobody
Created
Updated
Stars
★ (1)
Tags
Status-New
Type-Defect
Priority-Medium
Menel
on
Hi, I've installed mod_unified_push and mollysocket
I've freshly installed Molly Foss, and moved my data from signal.
I'm using an apache2 reverse proxy.
The service works and I get test notifications / push to Molly.
The mollysocket process is using i/o and cpu most of the time and the log is a constant stream of opening websocket to signal and closing again. I've attached all logs I could get, I can't interpret the molly android log myself.
The connection stays stable for a while, often when I send or receive a message, thenit startsxconstantly opening and closing websockets again.
The molly log I've attached is from a time where the websockets are constantly destroyed, at the end of thr log I send a message and it stopped for a while.
**If I switch to up.conversations.im or ntfy as distributor then the issue is gone**
Log:
[mollysocket-log.txt](https://github.com/user-attachments/files/18022870/2e3aa3f2-0d21-4678-976f-dc113069f362.txt)
debug log mollysocket:
[Mollysocket-debug.log.txt](https://github.com/user-attachments/files/18052560/log.txt)
Android Mollylog: https://github.com/user-attachments/files/18039531/06_12-15-36-30_229.log
Prosody mod_unified_push log:
[Prosody.log.txt](https://github.com/user-attachments/files/18047859/Prosody.log.txt)
I'm on Debian stable, mollysocket 1.5.4
Molly: v7.26.1-1-FOSS on CalyxOS on Nexus7 Android 15
The push server is mod_unified_push on prosody trunk updated 06.12.2024 the distributor is my xmpp app conversations.
I've first submitted the issue in the push server repository, but I think this is a mod_unified_push issue since it works with other push servers.
https://github.com/mollyim/mollyim-android/issues/407
They said:
It looks like they send a new endpoint everytime we register to it. We will avoid that loop on Molly. You should use the websocket for the moment to avoid draining your battery
Hi, I've installed mod_unified_push and mollysocket I've freshly installed Molly Foss, and moved my data from signal. I'm using an apache2 reverse proxy. The service works and I get test notifications / push to Molly. The mollysocket process is using i/o and cpu most of the time and the log is a constant stream of opening websocket to signal and closing again. I've attached all logs I could get, I can't interpret the molly android log myself. The connection stays stable for a while, often when I send or receive a message, thenit startsxconstantly opening and closing websockets again. The molly log I've attached is from a time where the websockets are constantly destroyed, at the end of thr log I send a message and it stopped for a while. **If I switch to up.conversations.im or ntfy as distributor then the issue is gone** Log: [mollysocket-log.txt](https://github.com/user-attachments/files/18022870/2e3aa3f2-0d21-4678-976f-dc113069f362.txt) debug log mollysocket: [Mollysocket-debug.log.txt](https://github.com/user-attachments/files/18052560/log.txt) Android Mollylog: https://github.com/user-attachments/files/18039531/06_12-15-36-30_229.log Prosody mod_unified_push log: [Prosody.log.txt](https://github.com/user-attachments/files/18047859/Prosody.log.txt) I'm on Debian stable, mollysocket 1.5.4 Molly: v7.26.1-1-FOSS on CalyxOS on Nexus7 Android 15 The push server is mod_unified_push on prosody trunk updated 06.12.2024 the distributor is my xmpp app conversations. I've first submitted the issue in the push server repository, but I think this is a mod_unified_push issue since it works with other push servers. https://github.com/mollyim/mollyim-android/issues/407
The main github issue I opened first before I realized it only happens with mod_unified_push is here: https://github.com/mollyim/mollysocket/issues/56
They said: It looks like they send a new endpoint everytime we register to it. We will avoid that loop on Molly. You should use the websocket for the moment to avoid draining your battery
Here I enabled push in fedilab, within one secomd we see a lot of push registrations , then it stops, not continuing the re-registering as above. But I think nornal would be only one registration? i think this may indicate that not only molly has a problem? https://share.snikket.de/vaG7I5xKYOL1kxqyDq6HBnmV/c6a9d887-d657-469e-9f97-08f9fd4d9190.txt