You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was running into a problem on my Mastodon instance with remote follows, getting an error "could not find redirect url" on my server. Turned out that the redirect URL is references on the web path of "/.well-known/host-meta/". And I had a rule in my nginx configs with the location /.well-known/ specified to redirect Let's Encrypt-related queries to a static directory. Turns out my redirect URL requests were getting redirected there. By making my Let's Encrypt directive more specific: location /.well-known/acme-challenge/ I was able to get the redirect request handled by the Mastodon app, and the redirects work now.
Might be worth mentioning in the setup docs that the path /.well-known/host-meta/ needs to be handled by the application!
Hope this helps someone!
The text was updated successfully, but these errors were encountered:
I was running into a problem on my Mastodon instance with remote follows, getting an error "could not find redirect url" on my server. Turned out that the redirect URL is references on the web path of "/.well-known/host-meta/". And I had a rule in my nginx configs with the
location /.well-known/
specified to redirect Let's Encrypt-related queries to a static directory. Turns out my redirect URL requests were getting redirected there. By making my Let's Encrypt directive more specific:location /.well-known/acme-challenge/
I was able to get the redirect request handled by the Mastodon app, and the redirects work now.Might be worth mentioning in the setup docs that the path
/.well-known/host-meta/
needs to be handled by the application!Hope this helps someone!
The text was updated successfully, but these errors were encountered: