#270 Issues with DMs

開啟中
aab2 年之前創建 · 4 條評論

In gnusocial.net, I've detected that most of sent DM don't arrive, regardless they are sent to GS, Mastodon or Pleroma. I'm gathering detailed logs, which I'll add here. But maybe this is one big clue, from ngingx logs:

PHP message: PHP Notice: Undefined property: Profile::$email in /var/www/gnusocial/lib/util/mail.php on line 634" while reading response header from upstream, client: 185.213.155.165, server: gnusocial.net, request: "POST /message/new HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "gnusocial.net", referrer: "https://gnusocial.net/user/outbox Another one:

PHP message: PHP Warning: Creating default object from empty value in /var/www/gnusocial/plugins/ActivityPub/classes/Activitypub_rsa.php on line 85" while reading response header from upstream, client: 199.58.83.11, server: gnusocial.net, request: "POST /message/new HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "gnusocial.net", referrer: "https://gnusocial.net/user/outbox

I've seen this message almost every time they are sent.

In gnusocial.net, I've detected that most of sent DM don't arrive, regardless they are sent to GS, Mastodon or Pleroma. I'm gathering detailed logs, which I'll add here. But maybe this is one big clue, from ngingx logs: PHP message: PHP Notice: Undefined property: Profile::$email in /var/www/gnusocial/lib/util/mail.php on line 634" while reading response header from upstream, client: 185.213.155.165, server: gnusocial.net, request: "POST /message/new HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "gnusocial.net", referrer: "https://gnusocial.net/user/outbox Another one: PHP message: PHP Warning: Creating default object from empty value in /var/www/gnusocial/plugins/ActivityPub/classes/Activitypub_rsa.php on line 85" while reading response header from upstream, client: 199.58.83.11, server: gnusocial.net, request: "POST /message/new HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "gnusocial.net", referrer: "https://gnusocial.net/user/outbox I've seen this message almost every time they are sent.
aab 評論 2 年之前'
發佈者

Ouch, bad mail config. Closing!!

Ouch, bad mail config. Closing!!
aab2 年之前 關閉
aab 評論 2 年之前'
發佈者

Ok, I'm reopening this with new info.

After fixing the mail config, the situation is this:

  • We can send and recieve DMs from Pleroma, both with notification (Pleroma in UI, GS in mail).
  • We can send and recieve DMs from Mastodon. We get the mail notification, but they don't get the UI one.
  • We can't send or recieve DMs internally; the "Undefined property: Profile::$email" mentioned before appears every time.
  • For Pleroma and Mastodon DMs to arrive, they have to write them as a new message. If they reply to one DM from our side, the reply does not arrive.

Maybe I'm not understanding it, but... Could it be some issue with webfinger? Is there any way to diagnose this?

Ok, I'm reopening this with new info. After fixing the mail config, the situation is this: - We can send and recieve DMs from Pleroma, both with notification (Pleroma in UI, GS in mail). - We can send and recieve DMs from Mastodon. We get the mail notification, but they don't get the UI one. - We can't send or recieve DMs internally; the "Undefined property: Profile::$email" mentioned before appears every time. - For Pleroma and Mastodon DMs to arrive, they have to write them as a new message. If they reply to one DM from our side, the reply does not arrive. Maybe I'm not understanding it, but... Could it be some issue with webfinger? Is there any way to diagnose this?
aab2 年之前 重新開啟
aab 評論 2 年之前'
發佈者

Today, after the GNUSocial 2.0.1-beta0 post.hillenius.net admin has fixed their "Messages" menu not showing, we've been able to exchange DMs. Good news! I'll try to figure out why it is not working between other 2 up to date GS servers (and, of course, if anyone has any clue, I'm happy to try anything).

Today, after the GNUSocial 2.0.1-beta0 post.hillenius.net admin has fixed their "Messages" menu not showing, we've been able to exchange DMs. Good news! I'll try to figure out why it is not working between other 2 up to date GS servers (and, of course, if anyone has any clue, I'm happy to try anything).
Diogo Cordeiro 評論 2 年之前'
所有者

Actually, there was a convention change with regard to how DMs are processed via ActivityPub... This was already considered in v3, but not in v2... :(

Actually, there was a convention change with regard to how DMs are processed via ActivityPub... This was already considered in v3, but not in v2... :(
登入 才能加入這對話。
未選擇里程碑
未指派成員
2 參與者
正在加載...
取消
保存
尚未有任何內容