Mastodon Remote Follow Button Opens Wrong Instance: Fix

When you click a remote follow button on a Mastodon profile, the browser sometimes opens the wrong instance for signing in. Instead of your home instance, the button redirects you to a different server where you have no account. This happens because the follow button uses a hardcoded URL that points to a specific instance rather than detecting your own. This article explains why the remote follow button misdirects users and provides step-by-step fixes for both visitors and instance administrators.

Why the Remote Follow Button Opens the Wrong Instance

The remote follow button is a hyperlink that contains a remote_follow parameter pointing to a specific Mastodon instance. Many profile pages and third-party tools embed this link with a static domain such as mastodon.social or a server chosen by the profile owner. When a visitor clicks the button, the browser sends them to that hardcoded instance rather than to their own home server.

Mastodon uses Web Finger and ActivityPub to resolve user identities across instances. The remote follow workflow expects the visitor to be on their home instance, where they are already authenticated. If the button bypasses that step and sends the visitor to an arbitrary server, the server cannot authenticate the user and either shows an error or prompts them to sign up on that wrong instance.

Instance administrators can configure a default redirect domain in their server settings. If that setting is left blank or points to a different server, the follow button will always open that domain instead of the visitor’s instance.

Steps to Fix the Wrong Instance Redirect

Fix for Visitors: Manually Edit the Follow URL

1. Click the remote follow button
   Do not close the new tab that opens. The address bar shows a URL similar to https://wronginstance.com/authorize_follow?acct=user%40example.com.
2. Copy the full URL
   Select the entire address including the acct parameter.
3. Replace the domain with your home instance
   Change https://wronginstance.com to https://yourhomeinstance.social. Leave the rest of the URL unchanged.
4. Press Enter to load the corrected URL
   Your home instance now receives the follow request. Sign in if prompted and confirm the follow.

Fix for Visitors: Use the Search Bar on Your Home Instance

1. Copy the full profile URL of the person you want to follow
   For example, https://otherinstance.social/@username.
2. Open your home instance in a browser
   Go to your own Mastodon server where you are already signed in.
3. Paste the profile URL into the search bar
   Click the search icon or press Ctrl+K. Paste the copied URL and press Enter.
4. Select the remote profile from search results
   Your instance performs a Web Finger lookup and displays the remote account. Click the profile name.
5. Click the follow button on the remote profile page
   This action sends a proper follow request from your home instance.

Fix for Instance Administrators: Configure the Default Redirect

1. Sign in to your Mastodon admin account
   You need administrator privileges on the server.
2. Open Administration > Server Settings
   Navigate to the server configuration panel.
3. Locate the Contact section
   Find the fields Site contact username and Site contact email.
4. Set the site contact username to a valid account on your instance
   Enter the username of an admin or moderator account that exists on your server. This ensures that the remote follow button defaults to your instance.
5. Save the changes
   Click the Save button at the bottom of the page. The remote follow button now redirects to your instance.

If the Remote Follow Button Still Opens the Wrong Instance

Browser Cache Stores the Old Redirect

Your browser may have cached the old follow link. Clear the cache for the domain that hosts the profile page. On Chrome, open Settings > Privacy and security > Clear browsing data. Select Cached images and files and clear data for the specific domain.

Third-Party Tools Embed a Static Link

Some profile badge generators and social media link tools create static follow URLs. These tools do not update when the instance changes. Replace the embedded link with a dynamic link that uses the remote_follow endpoint of the profile owner’s instance. The correct format is https://profileownersinstance.social/authorize_follow?acct=user%40theirinstance.com.

Instance Software Version Is Outdated

Older versions of Mastodon before 4.0 handled remote follow differently. If the instance runs an outdated release, the follow button may not respect the site contact settings. Update the instance to the latest stable version. Run git pull then RAILS_ENV=production bin/tootctl upgrade on the server.

Mastodon Remote Follow vs Manual Web Finger Search

Item	Remote Follow Button	Manual Web Finger Search
How it works	Browser redirects to a hardcoded instance URL	User pastes profile URL into home instance search
Authentication required	User must be signed in on the target instance	User is already signed in on home instance
Error rate on wrong instance	High if the URL points to a different server	Low because the home instance performs the lookup
Best for	Quick follow when both user and target are on the same server	Cross-instance follows and troubleshooting redirect errors

The remote follow button is convenient when both parties are on the same instance. For cross-instance follows, the manual Web Finger search is more reliable because it never sends the user to a wrong server. Instance administrators should verify that their site contact username is set correctly to reduce redirect errors for their users.