ntfy — Connect it to MokonyxSocial

This guide helps you connect ntfy so MokonyxSocial can push your Joomla content as a notification to an ntfy topic, reaching any device that's subscribed. Keep in mind ntfy is a lightweight notification service, not a social feed — your messages arrive as short push alerts (title, body, link), not formatted posts.

What you need

• An ntfy server — either the public ntfy.sh or your own self-hosted instance.
• A topic name to publish to. A topic is just a string; anyone who knows it can subscribe (or publish) unless your server enforces authentication.
• An access token, but only if your server or topic requires authentication. Public ntfy.sh topics don't need one.

Get your credentials

Server server (optional)

This is the base URL of your ntfy server. Leave it blank and MokonyxSocial uses the default public server, https://ntfy.sh.

Where to find it:

• Using the public server? Leave it blank, or type https://ntfy.sh.
• Self-hosting? Enter your instance's base URL, like https://ntfy.example.com — the same address where your ntfy web app lives (what you set as base-url in server.yml when you deployed it).

Access token token (optional)

This is a bearer token that authenticates your publishing. You only need it if your server has auth turned on and the topic is write-protected — public ntfy.sh topics don't require one.

Here's how to get it:

1. Sign in to your ntfy server's web app (ntfy.sh users: https://ntfy.sh/app; self-hosted: your own instance URL).
2. Go to Account → Access tokens (top-right account menu → "Access tokens").
3. Click Create access token, optionally add a label or expiry, and copy the token that's generated (it starts with tk_).
4. Make sure that token's user is allowed to publish to your target topic, then paste it into the token field.

Topic topic (required)

This is the topic name your messages publish to — subscribers listen on this exact name.

Here's how to set it:

1. Pick any topic name. On ntfy.sh it's created automatically the first time you publish, no signup needed. For privacy, choose something hard to guess, like moko-blog-8f3a2c.
2. Enter just the topic name (moko-blog-8f3a2c), not the full URL — the server field already provides the host.
3. On your phone or desktop, install the ntfy app and subscribe to the same topic (and same server) so the notifications reach you.

Set it up in MokonyxSocial

1. In Joomla admin, go to Components → MokonyxSocial → Services → New.
2. Choose ntfy.
3. Enter your credentials (topic is required; add server and token only if you need them).
4. Click Send Test to verify, then Save & Close and make sure it's Published.

Verify

Subscribe to your topic in the ntfy app, or open https://ntfy.sh/ (or your server's /) in a browser. After you hit Send Test or publish for real, the notification should pop up within a second or two.

Troubleshooting

• "403 Forbidden" when publishing — the topic needs auth. Add a valid token whose user can publish there, or switch to a public topic.
• Nothing arrives — you're subscribed to a different topic name or server than you published to. They have to match exactly (it's case-sensitive).
• "404" or connection refused — your server URL is wrong or your self-hosted instance is down. Double-check the base URL.
• The message body looks cut off — that's normal. ntfy messages are short push alerts, so long article bodies get trimmed and a link is added.

Notes & limits

• Topics are separated only by name, so on a public server anyone who knows your topic can read it. Use an unguessable name or an auth-protected topic if you need privacy.
• The default ntfy.sh has per-visitor rate limits; if you publish a lot, you may need your own server or a paid tier.
• ntfy is a notification channel, not an archive — messages are delivered and only briefly cached for offline subscribers.