Mastodon Error ‘Could Not Re-Federate Profile’ From Admin: Fix

When you run a Mastodon server and try to re-federate a user profile from the admin panel, you might see the error “Could not re-federate profile.” This error means the server failed to push the profile data to other instances in the fediverse. The cause is usually a temporary network issue, a misconfigured domain block, or a problem with the user’s account state in the database. This article explains why this error occurs and provides step-by-step fixes you can apply from the command line and the admin interface.

Why the Re-Federate Profile Action Fails in Mastodon Admin

The re-federate feature sends the user’s profile data to all known remote instances via ActivityPub. When you click “Re-federate” in the admin panel, Mastodon queues a background job in Sidekiq. If that job fails, the admin interface shows the error message.

Network connectivity problems

The Mastodon server must reach remote instances over HTTPS. If your server has a temporary DNS failure, a firewall rule blocking outbound connections, or a rate limit from a remote server, the re-federation job fails. This is the most common cause.

Domain blocks or silence settings

If your instance has a domain block or silence rule that affects the remote instance, the re-federation job cannot deliver the profile. The admin panel does not always warn you about existing blocks during re-federation.

Corrupted account state in the database

The user’s account record might have a stale “suspended” flag or a missing public key. This prevents the server from signing the ActivityPub payload correctly. The database inconsistency can happen after a failed migration or a partial import.

Steps to Fix the Re-Federate Profile Error in Mastodon Admin

Follow these steps in order. Start with the simplest fix and proceed to the more advanced commands only if needed.

1. Check Sidekiq queues for stuck push jobs
   Open your Sidekiq dashboard at https://yourinstance.com/sidekiq/queues. Look at the “push” queue. If you see many retrying or dead jobs, click “Clear retries” or “Clear dead” to remove them. Then go back to Admin > Moderation > Accounts, search for the user, and click “Re-federate” again.
2. Verify domain blocks and silence rules
   In Admin > Moderation > Domain blocks, check if you have any blocks or silence rules for the remote instances that should receive the profile. If you find a block, either remove it or set it to “No action” for the re-federation to work. After removing the block, try re-federating again from the user account page.
3. Restart the Sidekiq process
   SSH into your server. Run sudo systemctl restart sidekiq. This clears any stuck job processes. Wait 30 seconds, then retry the re-federate action in the admin panel.
4. Refresh the user account from the command line
   If the admin interface still fails, use the Mastodon CLI. SSH into your server as the mastodon user: sudo -u mastodon bash. Then run RAILS_ENV=production bin/tootctl accounts refresh USERNAME where USERNAME is the full handle including the domain (e.g., @user@example.com). This command rebuilds the user’s profile and sends it to all known remote instances.
5. Check the Mastodon log for detailed errors
   Run sudo journalctl -u mastodon-sidekiq -n 50 to see the last 50 lines of the Sidekiq log. Look for lines containing “Re-federate” or “PushService”. If you see a specific error like “Net::OpenTimeout” or “OpenSSL::SSL::SSLError”, that points to a network issue. If you see “ActiveRecord::RecordInvalid”, the account data is corrupt and you need to restore from a backup.
6. Re-federate all profiles on the instance as a last resort
   If only one user fails and the above steps did not work, run RAILS_ENV=production bin/tootctl accounts refresh --all. This re-federates every profile on your instance. It can take several minutes. After it finishes, check if the problematic user now works.

If Mastodon Still Shows the Re-Federate Error After These Fixes

“Re-federate” button is grayed out or missing

The button only appears for local users. If you are looking at a remote user’s profile, you cannot re-federate them. The admin interface only supports re-federation for users who registered on your instance.

Other users on the same instance also fail to re-federate

If multiple users fail, the issue is likely global. Check your server’s outbound connectivity by running curl -I https://mastodon.social from your server. If that fails, fix your firewall or DNS settings. Also check if your instance is rate-limited by large remote servers.

Re-federation succeeds but followers do not see updates

The re-federation action only pushes the profile, not the entire post history. If followers do not see new posts after re-federation, the user might have their account set to “Lock account” mode. Go to Preferences > Account > Privacy and safety and uncheck “Require follow requests.” Then re-federate again.

Re-Federate Profile Error: Admin Panel vs CLI Command

Item	Admin Panel (Re-federate button)	CLI Command (tootctl accounts refresh)
Interface	Web UI	Command line
Scope	Single user	Single user or all users
Error feedback	Generic “Could not re-federate profile”	Detailed error output to terminal
Dependency on Sidekiq	Yes, queues a background job	No, runs synchronously
Required access	Admin account	SSH access and mastodon user

The CLI command gives you more control and better error messages. Use it when the admin panel fails repeatedly. The admin panel is faster for one-off checks but provides less diagnostic information.

Now you can resolve the “Could not re-federate profile” error by checking Sidekiq queues, removing domain blocks, or using the CLI refresh command. Start with the Sidekiq queue inspection because it fixes most cases without requiring SSH access. If you manage multiple Mastodon servers, consider setting up a monitoring script that runs tootctl accounts refresh automatically for accounts that have not been re-federated in 24 hours.