[bug] Having issues federating with other instances.

[halphalp]

Describe the bug with a clear and concise description of what the bug is.

I was recently able to get GoToSocial up and running via Docker and everything seems to initially be working well using Caddy for a reverse proxy.

I'm able to post and have even had accounts on other instances follow me, but I cannot figure out how to follow or add other instances to my account/timeline (I'm running GTS as a single-user instance for just myself so I don't have to moderate other accounts).

One of the specific issues I'm experiencing is when I search for other accounts or instances on Lemmy/Mastodon, they appear with 0 toots, followers, and following, and following them doesn't seem to have an effect. I've tried this on various web and mobile clients, all with the same result.

I'm using the standard reverse proxy example for Caddy provided in the documentation. My config settings are largely unchanged aside from the few fields towards the top of the file that are specific to my instance (domain, host, etc.).

What's your GoToSocial Version?

v0.9.0 (Latest Docker tag)

GoToSocial Arch

Docker

What happened?

No response

What you expected to happen?

No response

How to reproduce it?

No response

Anything else we need to know?

No response

[tsmethurst]

following them doesn't seem to have an effect

Do you mean your follow gets stuck on 'follow requested'? Or something else?

It's normal that when you're on a new instance, it takes a while for your timelines to populate. Your instance won't go and fetch someone's posts, it waits for them to deliver them to you. So you should get new posts from people you follow, but old posts you'll have to dereference manually by copying the URLs for them and searching for them from your instance.

That said, we do have an issue open for fetching someone's posts from their outbox -- https://github.com/superseriousbusiness/gotosocial/issues/266 -- but it's not implemented just yet.

[halphalp]

Thanks for the insight. My follow gets stuck on 'follow requested' - I requested to follow a handful of sites a few days ago and all are still on 'follow requested'.

I'm happy to wait to see if things start coming together. However, is there a default amount of days where I should assume something is wrong with my setup if none of my follow requests go through?

[tsmethurst]

Hmmm if none of the follow requests go through that does indeed suggest something is wrong with your setup. You're not reusing a domain you'd already used before for a different fedi software, are you? Do you see anything interesting in the logs for your instance when you send a follow request? Could you try unfollowing and refollowing one of the accounts that's stuck on follow requested?

[sandboxgangster]

I also have the problem with instances that are not yet federated, for me it helps to unfollow, wait a bit and follow again, then it usually works after 1-2x

[gw31415]

I have the same issue. I failed to follow users and still on 'follow requested'.

[gw31415]

I have the same issue. I failed to follow users and still on 'follow requested'.

I've solved the problem. I configured Nginx to redirect htttp to https and now I can follow federated users.

[Mushus]

related? https://github.com/misskey-dev/misskey/issues/9435 signToActivityPubGet

[gw31415]

Oh, I've realized that I still haven't been able to successfully follow from Misskey and vice versa.

Update: Follow requests to Misskey accounts success in beta version: 0.10.0-rc1 git-2a99df0.

[natsukagami]

~~For Misskey.io specifically (not misskey.design nor misskey.art) I think they don't enable authenticated fetch on the instance. Trying to ask them about it but never got a response :(~~ They seem to have enabled it now.

[tsmethurst]

@halphalp is this still an issue for you?

[tsmethurst]

^^ Closed because I can't really replicate this without more info etc. But feel free to open again if you're still having problems and we can try and figure it out!