Because my first installation of Peertube had node core dump issues (running on OpenBSD), I decided to reinstall using a (supported) Debian VM. But I forgot to delete the Federation Follows from the first server before starting the second one.
So now, the Federation Follow requests are stucked in « Pending » state.
I have briefly restarted the old instance to delete the subscriptions. It seems the process as completed ok. Now this old instance is down. Only the new is on.
Still, I can’t subscribe to the initial instances I was looking for. I have tested new instances and subscription works ok.
Here’s a example of what the logs say:
Mar 06 20:08:49 peertube peertube[18548]: [peertube.example:443] 2024-03-06 20:08:49.328 info: 83.204.0.0 - - [06/Mar/2024:19:08:49 +0000] "POST /api/v1/server/following HTTP/1.0" 204 - "https://peertube.example/admin/follows/following-list" "Firefox"
Mar 06 20:08:49 peertube peertube[18548]: [peertube.example:443] 2024-03-06 20:08:49.348 info: Processing ActivityPub follow in job 8.
Mar 06 20:08:49 peertube peertube[18548]: [peertube.example:443] 2024-03-06 20:08:49.456 info: Creating job to send follow request to https://videos.danksquad.org/accounts/peertube.
Mar 06 20:08:49 peertube peertube[18548]: [peertube.example:443] 2024-03-06 20:08:49.515 info: Processing ActivityPub unicast in job 18.
Mar 06 20:08:50 peertube peertube[18548]: [peertube.example:443] 2024-03-06 20:08:50.138 info: Updating 0 good actor follows and 1 bad actor follows scores in cache. {
Mar 06 20:08:50 peertube peertube[18548]: "badInboxes": [
Mar 06 20:08:50 peertube peertube[18548]: "https://videos.danksquad.org/accounts/peertube/inbox"
Mar 06 20:08:50 peertube peertube[18548]: ]
Mar 06 20:08:50 peertube peertube[18548]: }
I there a way to solve this?
Thanks.