Configure Fediverse Component Options

Overview

Configure the global Fediverse options so remote servers can find your site and the background workers can process activity reliably. These settings give the site a stable public identity and prevent common discovery and delivery failures.

You usually need this setup immediately after activating the core plugins. Without these values, the dashboard diagnostics stay incomplete and remote servers may not be able to resolve local actors correctly. After you finish, the site has a usable baseline for discovery, delivery, worker execution, and follow handling.

Before you begin

Core plugins should already be enabled.
You need administrator permission to edit component options.
Decide the public URL the Fediverse should expose to remote servers. This must be the real external site address, not an internal container or localhost address.
Decide whether new incoming follows should be accepted automatically, reviewed manually, or rejected.

Steps

Open Components -> Fediverse.
Click Options in the toolbar.
Configure the required fields in the main options form.
- Public base URL - The canonical public site URL that remote servers use for discovery, actor lookups, and federation endpoints. Use the externally reachable URL of the site.
- Actor handle format - The template used to build local Fediverse handles. Choose a format that produces stable, predictable handles for your Joomla users.
- Key rotation interval (days) - The number of days between automatic signing-key rotations. This only matters if key rotation is part of your operational setup.
- Enable inbox worker - Allows background processing of inbound federation activity such as replies and reactions.
- Enable delivery worker - Allows background processing of outbound deliveries to remote followers.
- Follow policy - Sets the default behavior for new follow requests. Use Open to accept automatically, Manual approval to review follows, or Closed to reject them by default.
Optional: review the retention settings.
- Inbox retention (days) - Controls how long inbound records are kept before cleanup removes old entries.
- Outbox retention (days) - Controls how long outbound activity history is kept.
- Delivery queue retention (days) - Controls how long completed or old delivery queue data remains available.
Optional: configure the License tab if you need paid features.
- License Key - Paste the LemonSqueezy key issued for this site and save the options to activate the installation.
- If the site was moved or restored from backup, follow the note in the License tab to clear the old binding before saving the key again.
Click Save & Close.
Optional: open the Governance tab.
- Strict action permissions - Use this when you want explicit Fediverse permissions for sensitive administrator actions.
- If you enable strict action permissions, open the Permissions tab afterwards and grant the detailed Fediverse actions to the right Joomla groups. Otherwise editors or managers can lose access to moderation and other Fediverse administration tasks.
Reopen the options screen once to confirm the values persisted.

Check your result

The saved values remain present after reopening the options screen.
The Public Base URL diagnostics check on the dashboard passes.
Inbox and delivery processing can run once the scheduler tasks are active.
New follow requests are handled according to the selected default policy.
Paid features become available if a valid paid license was saved.

Troubleshooting

Remote servers cannot discover local actors

Likely cause: Public base URL is incorrect, not public, or does not match the site’s real external address.
Solution: Correct the URL in component options, save it again, and rerun the dashboard diagnostics.

Publishing works, but nothing is delivered

Likely cause: Enable delivery worker is disabled or the scheduler tasks are not active.
Solution: Turn on the delivery worker in component options and verify the Fediverse scheduler tasks are enabled.

Replies and reactions never appear

Likely cause: Enable inbox worker is disabled or the inbox worker task is not running.
Solution: Turn on the inbox worker in component options and verify the scheduler configuration.