I originally signed up to mastodonapp.uk. Now that I’m attempting to get m.dollha.us running, I’m looking to pull my account from the former and move it to the latter. Easier said than done, though, because I cannot, for the life of me, seem to get my instance to federate with that instance. I have tried leaving it for a week or three, I have tried starting it in limited federation mode and whitelisting the instance in question, and I have tried a dedicated relay provided by fedi.buzz.
Today I noticed something interesting in my sidekiq logs: My instance is actively rejecting mastodonapp.uk - despite it not being in any blocklists. This is, of course, via the dedicated relay, so it could be a relay issue, but I can see no obvious reason why that would occur.
What could be the problem here?
A relay, as in the Mastodon relay feature? As in Administration->Relays? If so, does mastodonapp.uk have an active relay? It can’t be used to connect to just any Mastodon server. It has to connect to a special relay server.
Not sure whether this is helpful.
fedibuzz alleges that you can follow a single specific instance with their relay, and I see nothing to suggest that I can’t use it better federate with mastodonapp.
I did note, though, that both my instance and mastodonapp are connected to relay.intahnet.co.uk - and whilst it has a few issues in the logs, it has none since i reset the instance again after attempting limited federation mode.
Yes, it claims to proxy the traffic, but then you have to connect to the fedibuzz relay server.
It sounded from the post that there was an attempt to directly connect to a Mastodon server through the relay connection, which won’t work.
Oh, no, sorry. I mean that I can’t appear to get any posts from mastodonapp.uk, whether by relay or federation
Time to read the code and debug it.
When you find the cause, open a bug report with the project.
But ruby is so hard :(
I come from c# land and my skills are soft and squishy
Meh, code is code, just read the logic and follow the function calls.
