dariusk / rss-to-activitypub

An RSS to ActivityPub converter.
MIT License
556 stars 27 forks source link

rss-to-activitypub running but unable to follow #56

Open Roelofpieter opened 4 years ago

Roelofpieter commented 4 years ago

Hi there. I have installed rss-to-activitypub on a Raspberry Pi at home. After some initial struggles (I had to downgrade nodejs to v10.) it seems to be running. I can enter a RSS feed and it gets converted to AP. I can view the account and it's posts from my Pleroma account. Yaj! I seem however unable to follow the feed. When I try to follow the feed from my Pleroma account I see the status "Request sent". It stays that way, even after an hour waiting. I do see ["https://server.domain.tld/users/username"] added to the accounts table, so apparently the following request gets registered by rss-to-activitypub.

I can imagine two causes:

  1. Rss-to-activitypub runs on the same machine as my Pleroma install, (it gets called under a different hostname). Since both Pleroma as rss-to-activitypub have to speak Activitypub, I can image this not working?
  2. I have rss-to-activitypub proxied behind nginx. Perhaps this can lead to this problem?

I hope someone can comment on these guesses? Or can there be another cause here?

dariusk commented 4 years ago

Hi -- I have been having consistent issues getting follows from Pleroma to work. What version of Pleroma are you running? (Sorry for the delay but, you know, pandemic and everything has me behind on my email.)

hieronymousch commented 4 years ago

I seem to have the same problem with both runniing on seperate machines. They communicate but following is not working. I get this error when following: 18:32:12.681 [error] Follower/Following counter update for https://XXXXxyz/u/PrusaPrintersBlogRSS failed. Aug 29 18:32:12 XXX pleroma[1768]: {:error, "id must be a string"} The RSS side seems to validate the follow correctly but shows also pending... Pleroma database of users recognizes the RSS user...

hieronymousch commented 4 years ago

Just upgraded my Pleroma to 2.1.1 and problem still exists.

umonaca commented 3 years ago

I have fixed it here: https://github.com/dariusk/rss-to-activitypub/pull/59