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:
- 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?
- 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?
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:
I hope someone can comment on these guesses? Or can there be another cause here?