I’ve noticed that whenever I post from my instance (midwest.social) to lemmy.ml that the upvotes don’t match that of what’s on lemmy.ml and the comments don’t show up for a while.
You might want to change the log level for Lemmy to warn or error. I also checked the logs on our side just now, but there were no errors for midwest.social.
That one is probably harmless, it just means that the activity was already received and processed before. It is strange though that Lemmy on your instance would send the same activity twice.
Earlier I changed lemmy.ml logs to warn in docker-compose.yml and ran docker-compose up -d. Since then it has collected some better logs:
I suggest you follow the same steps for logging (with grep lemmy.ml), and see more useful log entries. In this case it looks like midwest.social is sometimes unreachable. In theory Lemmy will retry a few times, but that isnt really tested. And there are some weird public key errors, which should have more information in your logs.
It could be this issue, but hard to say. Do you notice any errors in your Lemmy logs?
Sorry, which command do I need to run to get those?
sudo docker-compose logs -f --tail=100 lemmy
You might want to change the log level for Lemmy to warn or error. I also checked the logs on our side just now, but there were no errors for midwest.social.
lemmy_1 | 2022-01-12T21:46:01.367000Z WARN lemmy_apub_lib::activity_queue: Send https://midwest.social/activities/announce/d268e800-2ed3-42ba-8014-634373b46a96 to https://lemmy.ml/inbox failed with status 400 Bad Request: Failed to insert activity into database: duplicate key value violates unique constraint “idx_activity_ap_id”
That one is probably harmless, it just means that the activity was already received and processed before. It is strange though that Lemmy on your instance would send the same activity twice.
Earlier I changed lemmy.ml logs to warn in docker-compose.yml and ran
docker-compose up -d. Since then it has collected some better logs:I suggest you follow the same steps for logging (with grep lemmy.ml), and see more useful log entries. In this case it looks like midwest.social is sometimes unreachable. In theory Lemmy will retry a few times, but that isnt really tested. And there are some weird public key errors, which should have more information in your logs.