I just stumbled upon this as well. At least for the email verification part. It seems one of the last releases has added email addresses for accounts and I wanted to add this to mine, but apart from this log line: 2026/07/10 11:09:58 INFO Resending email verification (email=xx@xx.eu, http_method=POST, http_path=/v1/account/email/resend, tag=account, user_id=xx, user_name=felix, visitor_auth_attempts_remaining=30, visitor_emails=2, visitor_emails_limit=24, visitor_emails_remaining=22, visitor_id=ip:xxx, visitor_ip=xxx, visitor_messages=0, visitor_messages_limit=17280, visitor_messages_remaining=17280, visitor_requests_remaining=19, visitor_seen=2026-07-10T11:09:58.274Z, visitor_topic_creations_remaining=92) Nothing else happens. I also dont see any logging regarding this in the Cloudron event log for email.

@jdaviescoates said in Add UnifiedPush settings in documentation: I could be missing something and I'm not even using the app, but just because I'd guess most people would want UnifiedPush stuff on in an app that's all about getting notified about stuff. Unifiedpush is not used to send you notifications from Ntfy, but unifiedpush is a system that can use your ntfy server to relay notifications from apps through it, instead of using Google infrastructure for these. The list of supported software can be found at https://unifiedpush.org/users/apps/, but at least when testing this with NeoChat I not only needed give write access to up_*, but also read access. @mononym said in Add UnifiedPush settings in documentation: When choosing ntfy as UnifiedPush the app created some random string (i.e. the ntfy topic) and it starts with up. In the end, it is difficult to guess the topic name as it is random and as long you're not subscribed to that topic, you won't see the messages as well. Basically, write-only access is not enough to use the nfty server like a public instance as credentials are necessary to read the topic. What I personally find difficult with Unifiedpush is giving the whole world the ability to send data (text and files) to your server. There are too many bad actors on the internet for this to be a good idea.

@lukas said in NTFY app overview always says "connecting...": Btw.: I switched in Element App to NextPush and this works fine. With me it's actually the other way around. I've been using ntfy for Element Push but I'd like to install NextPush for Nextcloud talk notifications but can't get it to work. I'm sure it's some trivial thing that's missing but I can't find any proper documentation on setting it up. Would you mind sharing the steps you took? I have installed the App on the NC-Level and on my mobile device. Logged in on my device, it shows up in the backend of the NC-Level App but won't display notifications.

@AmbroiseUnly thanks for reporting, fixed.

@Recliner2042 I use NTFY for push notifications on my Elements install with Android based clients. Should work for IOS as well. It's running very smooth for more than a year... [image: 1714887159268-image-1678369653409.png] Here's what i did to make this work: To make use of your ntfy installation, on Android for example, you need two things: the ntfy app: a UnifiedPush-compatible matrix app You need to install the ntfy app on each device on which you want to receive push notifications through your ntfy server. The ntfy app will provide UnifiedPush notifications to any number of UnifiedPush-compatible messaging apps installed on the same device. Setting up the ntfy Android app: Install the ntfy Android app from F-droid or Google Play. In its Settings -> General: Default server, enter your ntfy server URL, such as https://ntfy.DOMAIN. In its Settings -> Advanced: Connection protocol, choose WebSockets. That is all you need to do in the ntfy app. In particular you do not need to follow any instructions about subscribing to a notification topic as UnifiedPush will do that automatically. Setting up a UnifiedPush-compatible matrix app: Install any UnifiedPush-enabled matrix app on that same device. The matrix app will learn from the ntfy app that you have configured UnifiedPush on this device, and then it will tell your matrix server to use it. Steps needed for specific matrix apps: FluffyChat-android: Should auto-detect and use it. No manual settings. SchildiChat-android: enable Settings -> Notifications -> UnifiedPush: Force custom push gateway. choose Settings -> Notifications -> UnifiedPush: Re-register push distributor. (For info, a more complex alternative to achieve the same is: delete the relevant unifiedpush registration in ntfy app, force-close SchildiChat, re-open it.) verify Settings -> Notifications -> UnifiedPush. Element-android: choose Settings -> Notifications -> Notification method -> ntfy verify Settings -> Troubleshoot -> Troubleshoot notification settings If the matrix app asks, "Choose a distributor: FCM Fallback or ntfy", then choose "ntfy". If the matrix app doesn't seem to pick it up, try restarting it. Cheers

@lukas in the settings page [image: 1714490711765-f48c514e-1d2b-4323-9260-6f478c40fb1c-image-resized.png]

@girish It ended up not working. I didn't investigate it too much. I just recreated the app and copied the database over.

Updated!

@timconsidine i think that's because it remembers the password for the second time. All topics are protected by default. This is a deviation from the ntfy default since we don't want unprotected instance. See https://docs.cloudron.io/apps/ntfy/#access-control . auth-default-access has to be changed .

@girish Now I can see it, too. Thanks! I'll give it a try. Update: Works great. Tested with Element and Fedilab so far.