List a self-hosted instance
FluxerList lists community-run, self-hosted Fluxer instances so people who want to run their own communities can find a real, working deployment to register on.
An instance listing points people at infrastructure you control, not at a server invite, so it is held to a different bar. It has to be reachable, run genuine Fluxer software, and be provably owned by whoever submitted it before it goes live.
Any signed-in user can submit an instance. Domain verification is still required before a listing goes public. Admins can turn submissions off platform-wide, or restrict them to users granted Instance Tester access, so if you don’t see the option, ask in the support server.
What you’ll need
You can also add an icon, a banner, a Markdown “About this instance” section, up to 5 tags, a primary language, and website, support, and source links. Your operator contact is never shown publicly and can be a Fluxer username, a social handle, or any other reliable contact method.
The health check
The check runs the moment you submit, and again whenever you select Re-run Health Check in your dashboard. A failed check doesn’t reject your submission. Fix your instance and recheck without resubmitting the domain.
The result shows TLS status, each probe’s pass or fail, and every field your descriptor returns. When a TLS or connection check fails, you see a short reason such as “SSL failed”, “Certificate expired”, or “Domain not found” instead of raw network error text.
Verify your domain
Domain verification is a hard requirement. An instance can’t be approved or shown publicly until you prove you control the domain. Anyone could type in a domain they don’t run, and this is how FluxerList confirms you do.
Request a token
From the Add Instance success screen or your dashboard’s Domain Verification panel, request a token. FluxerList generates a DNS TXT record name and value for your domain.
Add the DNS TXT record
Create it with your DNS provider exactly as shown. Copy the values from the panel rather than typing them.
A verification token is valid for 7 days. If it expires, request a new one. That invalidates the old token, so always use the latest value.
Repeated checks don’t speed up DNS propagation. Wait a few minutes between attempts. A stray space or a truncated value is the most common reason a check fails.
What the badge means
The Domain Verified badge confirms domain ownership only. It is not an endorsement of the instance’s content, moderation, or reliability by Fluxer or FluxerList, and it is deliberately styled differently from the server Verified badge.
Review stages
After you’re live
Every listed instance is re-checked weekly for health and TLS. If a check fails, the instance is pulled from Browse Instances until it passes again, and you are notified. You can re-run the check yourself from your dashboard once you’ve fixed the problem.
Each public page carries a disclaimer that self-hosted instances are run independently and are not operated by FluxerList. Anyone can report a misleading listing, an unreachable instance, or an unresponsive operator, and reports go through the same review queue as servers, bots, and themes.
You can delete a pending instance from your dashboard’s Instances tab. Approved instances stay locked so a live listing can’t disappear from Browse without a moderator noticing.
Tips to get listed faster
- Deploy fully before submitting. A half-configured install can’t pass.
- Request your token and add the TXT record right after submitting, so propagation isn’t what you’re waiting on.
- Keep your operator contact current. It’s how reviewers reach you.
- If a check fails, fix the instance and re-run it instead of submitting a duplicate.