Mastodon: People on other instances cannot remote follow me on my instance.

[colegleason]

When people from another instance (mastodon.cloud or mstdn.io) try to follow me (cmu.party), they receive "422 Remote account could not be resolved". When trying to press the button on my web profile, they get the error page. Where would I look in the logs to find this issue?

---

• [x] I searched or browsed the repo’s other issues to ensure this is not a duplicate. (There are other issues about remote follow, but this seems to be the reverse issue)

[colegleason]

This might be related to #960, as I also see "Could not find the required redirect URL for your account" when trying to remote someone from another instance through the web form.

[mjankowski]

Are you using "@[email protected]" or just "[email protected]" (the latter will work, the former will probably error)?

[colegleason]

neither seem to work

On Fri, Apr 7, 2017 at 2:29 PM Matt Jankowski [e-mail]
wrote:

Are you using "@[email protected]" or just "[email protected]"
(the latter will work, the former will probably error)?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tootsuite/mastodon/issues/1185#issuecomment-292630527,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOLh1pDnfxa9mc5VeGqlMGVYVMLDf1pks5rto6egaJpZM4M3PXv
.

[colegleason]

I replaced my nginx config with the one in the Production guide exactly and this works now. My SSL redirect may have been misconfigured.

[sys0dm1n]

I had the same issue, by removing let's Encypt location block everything worked fine:
location ~ /.well-known {
allow all;
}
I hope this might help others with my case.

[anieto]

Sys0dm1n where exactly would find and remove the letsencrypt block? I'm having the same issues listed above and none of the suggestions have helped

[sys0dm1n]

@anieto Usually this should be in your Apache/Nginx Virtualhost configuration file under sites-enabled/ folder.
If you have used Let's Encrypt, what are the steps that you went through ?

[sincoew]

Thanks colegleason and sys0dm1n,
I had the same issue and fix now.

[fweng322]

@sys0dm1n provided the solution. Also, the /.well-known/ alias for Let's Encrypt works only in http:// not in https://, so I just removed the alias in https settings and this problem is solved. Thanks.