I have an instance of go-to-social that has been off for a long time and had been "expired" by most other instances. Even my own Mastodon instance doesn't recognize it (can't even search for my account on it).
-
I have an instance of go-to-social that has been off for a long time and had been "expired" by most other instances. Even my own Mastodon instance doesn't recognize it (can't even search for my account on it).
Is there any way to salvage it, or is it just done?
-
BeAware :fediverse:replied to Steve Dinn on last edited by
@steve maybe it's worth adding the GoToSocial tag as well? The dev browses that tag regularly and maybe could offer some advice.
-
@steve On your Mastodon instance, if you go into Preferences > Moderation > Federation, set the Moderation setting at the top to All and search for your GoToSocial instance, does it come up? If it does and you click into it, you may see a message down at the bottom about failed delivery attempts and such.
-
@hybridhavoc Yeah, I found it. I see these options, but I've since posted from my GTS account (a DM to my Mastodon account) and that didn't restart anything.
Going to try clicking that "Restart delivery" link, but it'll be a problem if every other instance has to click it too.
-
Has the job run in Mastodon yet?
It may take time for the job to run before it is salvaged.
I am not sure how often it does that job on Mastodon. Once or twice a day, I recall someone saying once.
I believe once we start getting your posts it will start at some point automatically.
-
@paul @hybridhavoc My GTS instance went into a failed state again according to my Mastodon instance. I'm not sure why. They're actually running on the same VM, both in docker containers.
-
After sending a DM from GTS to Mastodon, and inspecting the logs, I see this outgoing request from GTS:
`method=POST url=https://social.dinn.ca/inbox contentType="application/ld+json; profile=\"https://www.w3.org/ns/activitystreams\"" attempt=0 pubKeyID=https://gts.dinn.ca/users/steve/main-key msg="401 Unauthorized" `And the corresponding line in the mastodon web log:
`POST /inbox HTTP/2.0 401 162 "" "Go-http-client/2.0"` -
@[email protected] @hybridhavoc
It's not showing an error in my instance. Cc @[email protected]
I'm tagging and will look at my logs for push and pull errors