-
-
Notifications
You must be signed in to change notification settings - Fork 7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relay usage “Rejected Announce activity” #10324
Comments
I thought I'd give the relay feature a try but it's not working for me either. I'm running v2.7.4 and tried the same relays and a few others and seeing the same messages in my logs as well. |
I'm kinda curious about this too, does someone have any idea what would cause this? 👀 |
This is a bit odd, because I don't believe the pub-relay sends The messages in your logs have an I don't know what code those relays are running, but it's not what we expect. |
They seem to be running https://git.pleroma.social/pleroma/relay which claims to be Mastodon compatible, I guess it's not? |
I put up a 2.7.0 instance and it worked fine with my relay as well as the one at relay.mastodon.host, so clearly some commit between then and now botched pleroma relay support. Gonna continue to narrow down when it broke. Btw are there any known masto relays that I could try? Just curious if relay support in general is broken Edit: It broke at 2.7.2 Edit2: The problem is commit 6c11f0f. It's the oldest commit that caused all fedi tl activity to stop. I have no ruby experience though, so I still don't know the exact problem |
I believe the latest version of both work together. My friend has a relay here —> https://relay.cloutfla.re/ and it’s working fine. The only issue they’ve had is it doesn’t register pleroma instances properly sometimes. I’m not sure but give that relay a try if you wanna test it, it works for me and others :)
Appreciate you guys helping with this ❤️
… On 27 Mar 2019, at 00:50, Izalia Mae ***@***.***> wrote:
I put up a 2.7.0 instance and it worked fine with my relay as well as the one at relay.mastodon.host, so clearly some commit between then and now botched pleroma relay support. Gonna continue to narrow down when it broke.
Btw are there any known masto relays that I could try? Just curious if relay support in general is broken
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Right, the abuse filter added in 2.7.2 did not foresee Announces from relays, since that's now how pub-relay works. But there's nothing wrong with doing it via Announces, so I will submit a fix. |
Thanks @Gargron for the quick fix! |
Thank you for the quick fix Gargron! I just manually applied it to my instance and it's perfect! If anyone else wants to do the same, just apply the changes ^ to your local install and restart ❤️ |
Thanks, works for me! |
While this does get pleroma relays working again, it spams sidekiq with errors. Here's the full error
|
Sorry to re-open this. I am experiencing same thing. I have hundreds of these "Rejected Announce activity" logs:
I can't get this relay to be enabled. I remember it used to work before (when I had former version of Mastodon). Now I am running the last version (4.1.2). I opened ports 80,443 to that domain (relay.c.im), and I also tested to see if I can call URL statuses or users from c.im in the search field, and it worked. |
As https://discourse.joinmastodon.org didn't help I'm writing here:
I try to use relays and I get log entries like this:
what am I doing wrong?
The logs read actor but I subscribed inbox …
What I'm talking about is this:
The text was updated successfully, but these errors were encountered: