push notification errors are flooding my logs #686

New issue

Closed

opened 2025-02-07 22:29:44 +00:00 by coztellation · 7 comments

coztellation commented

2025-02-07 22:29:44 +00:00

(Migrated from github.com)

i logged in on ubports's cinny webapp and then later wiped that device, and since then my logs have been absolutely flooded with
homeserver-1 | 2025-02-07T22:05:36.519352Z ERROR sender:push{userid="<me>" pushkey="<key>"}:send_push_notice:send_notice:send_request: conduit_service::pusher: Push gateway https://push.ubports.com:5003 returned invalid response: deserialization failed: missing field rejected at line 1 column 2
errors
sometimes the pushkey field is empty and i get
homeserver-1 | 2025-02-07T22:07:07.857411Z ERROR sender:push{userid="<me>" pushkey=""}:send_push_notice:send_notice:send_request: conduit_service::pusher: Push gateway https://push.ubports.com:5003 returned invalid response: deserialization failed: missing field rejected at line 1 column 2

i'm running in docker, notifications work for some people but not others (but that's not the specific issue here), federation is completely off if that changes anything, everything else in my configs looks more or less standard

i can't seem to find any way to scrub push.ubports.com off of the list of push notification targets, or find any other solution
i also couldn't find any issues similar to this on either these issues or conduit's gitlab

i logged in on ubports's cinny webapp and then later wiped that device, and since then my logs have been absolutely flooded with `homeserver-1 | 2025-02-07T22:05:36.519352Z ERROR sender:push{userid="<me>" pushkey="<key>"}:send_push_notice:send_notice:send_request: conduit_service::pusher: Push gateway https://push.ubports.com:5003 returned invalid response: deserialization failed: missing field `rejected` at line 1 column 2` errors sometimes the pushkey field is empty and i get `homeserver-1 | 2025-02-07T22:07:07.857411Z ERROR sender:push{userid="<me>" pushkey=""}:send_push_notice:send_notice:send_request: conduit_service::pusher: Push gateway https://push.ubports.com:5003 returned invalid response: deserialization failed: missing field `rejected` at line 1 column 2` i'm running in docker, notifications work for some people but not others (but that's not the specific issue here), federation is completely off if that changes anything, everything else in my configs looks more or less standard i can't seem to find any way to scrub push.ubports.com off of the list of push notification targets, or find any other solution i also couldn't find any issues similar to this on either these issues or conduit's gitlab

morguldir commented

2025-02-07 22:33:43 +00:00

(Migrated from github.com)

Fluffychat can (almost) delete notification targets from any of your sessions

Which client was this? My first guess is that ubports doesn't implement the push gateway spec

Fluffychat can (almost) delete notification targets from any of your sessions Which client was this? My first guess is that ubports doesn't implement the push gateway spec

girlbossceo commented

2025-02-08 00:23:48 +00:00

(Migrated from github.com)

Synapse doesn't seem to get unhappy when this happens, so we'll copy this behaviour and the error logs should at least go away.

Can you try the latest rc3 I have just tagged? It seems to be an issue with the push gateway software only returning an empty JSON body, missing the required field "rejected": https://github.com/Flohack74/matrix-pushgw/blob/ubuntu-push-module/matrix-pushgw.go#L152 Synapse doesn't seem to get unhappy when this happens, so we'll copy this behaviour and the error logs should at least go away.

coztellation commented

2025-02-08 11:00:30 +00:00

(Migrated from github.com)

fluffychat does appear to show and let me delete the thing !! thank you !!!! although. in the interest of testing 0.5.0-rc3 i've not done that quite yet

from what i recall it was the cinny webapp on the openstore !!
https://open-store.io/app/cinnyweb.nuno this one, to be specific
fluffychat shows the notification endpoint as

Cinny Ubuntu Touch -
cinny.nitanmarcel_cinny
https://push.ubports.com:5003/_matrix/push/v1/notify

i can't seem to find a docker tag/image for release candidate 3 though. putting girlbossceo/conduwuit:v0.5.0-rc3 as listed in the github versions didn't work, so i looked on docker hub and the search feature doesn't show anything labelled rc3 whereas there's rc2 and rc in the list if you search for them

fluffychat does appear to show and let me delete the thing !! thank you !!!! although. in the interest of testing 0.5.0-rc3 i've not done that quite yet from what i recall it was the cinny webapp on the openstore !! https://open-store.io/app/cinnyweb.nuno this one, to be specific fluffychat shows the notification endpoint as ``` Cinny Ubuntu Touch - cinny.nitanmarcel_cinny https://push.ubports.com:5003/_matrix/push/v1/notify ``` i can't seem to find a docker tag/image for release candidate 3 though. putting girlbossceo/conduwuit:v0.5.0-rc3 as listed in the github versions didn't work, so i looked on docker hub and the search feature doesn't show anything labelled rc3 whereas there's rc2 and rc in the list if you search for them

girlbossceo commented

2025-02-08 13:31:32 +00:00

(Migrated from github.com)

Yeah there was an untested CI edge case bug I need to fix, sorry :<

👍 1

girlbossceo commented

2025-02-09 22:36:04 +00:00

(Migrated from github.com)

Can you try pulling rc3 again?

Volki-57 commented

2025-02-10 00:29:06 +00:00

(Migrated from github.com)