No notifications with nextpush or sunup with fdroid Jami client

hazematman · November 8, 2025, 12:36am

Hello, I’ve just started using Jami and I was trying to setup push notifications on my android phone. In the app I have unifiedpush enabled and the DHT proxy but with these options enabled I don’t seem to receive any messages at all. My device won’t even load messages with the app open. Only when I switch to local DHT node do I start receiving messages and notifications.

Is there anything else you need to to get push notifications working?

Rubus_chiliadenus · November 10, 2025, 11:52am

OpenDHT isn’t compatible with UnifiedPush AND_3, it doesn’t implement Web Push.

hazematman · November 10, 2025, 5:48pm

So basically unified push doesn’t work in Jami even though the client displays it as an option?

Rubus_chiliadenus · November 10, 2025, 6:36pm

Maybe some legacy UnifiedPush distributors work… If they follow the legacy UnifiedPush specifications…

Rubus_chiliadenus · November 11, 2025, 5:16pm

@Jami Can you try the workaround from Specification compliance status?

A temporary hack is to set content-encoding to aes128gcm and add TTL header, it should be seen as a valid web push message. If the message doesn’t contain any sensitive information, that 's OK.

hazematman · November 11, 2025, 5:55pm

I don’t know much about Jami/OpenDHT, but from a quick glance it looks like the headers for a unified push request can be modified here

github.com/savoirfairelinux/opendht

src/dht_proxy_server.cpp

master


      
          
          unsigned reqid = 0;
          try {
              std::shared_ptr<http::Request> request;
              http::Url tokenUrl(token);
              if (type == PushType::UnifiedPush)
                  request = std::make_shared<http::Request>(io_context(), tokenUrl.protocol + "://" + tokenUrl.host + (tokenUrl.service.empty() ? "" : (":" + tokenUrl.service)), logger_);
              else
                  request = std::make_shared<http::Request>(io_context(), pushHostPort_.first, pushHostPort_.second, pushHostPort_.first.find("https://") == 0, logger_);;
              reqid = request->id();
              request->set_target(type == PushType::UnifiedPush ? (tokenUrl.target) : "/api/push");
              request->set_method(restinio::http_method_post());
              request->set_header_field(restinio::http_field_t::host, type == PushType::UnifiedPush ? tokenUrl.host.c_str() : pushServer_.c_str());
              request->set_header_field(restinio::http_field_t::user_agent, "RESTinio client");
              request->set_header_field(restinio::http_field_t::accept, "*/*");
              request->set_header_field(restinio::http_field_t::content_type, "application/json");
          
              if (type == PushType::UnifiedPush) {
                  Json::Value notification(Json::objectValue);
                  notification["message"] = Json::writeString(jsonBuilder_, std::move(json));
                  notification["topic"] = token;

If jami doesn’t respond I think I may look at running my own proxy with the workaround suggested above.

hazematman · November 12, 2025, 11:41pm

So I decided to test this out myself and the workaround seems to work! I have a self hosted OpenDHT proxy running with the changes in this PR and I am able to get push notifications on my device when I connect to my self hosted proxy.

github.com/savoirfairelinux/opendht

Modify UnifiedPush post request to be AND_3 compliant

master ← Hazematman:fix_unified_push

opened 11:40PM - 12 Nov 25 UTC

Hazematman

+11 -1

UnifiedPush AND_3 spec requires that server-to-server communication use encrypte…d WebPush requests. Currently the OpenDHT proxy does not do that. Following the advice in this issue https://codeberg.org/UnifiedPush/wishlist/issues/22 this PR worksaround the issue by making the request look like a real encrypted WebPush request following the example the FindMyDevice server is using https://gitlab.com/fmd-foss/fmd-server/-/merge_requests/101 This should be okay as the actual message contents are e2ee (to my knowledge) so if we just mark the payload as encrypted we can make unifiedpush servers happy.

W192547975 · November 29, 2025, 1:42pm

Excuse me, is it possible to set a timer through a serverless fake distributor to wake up a client operating in local DHT node mode?

W192547975 · November 29, 2025, 1:43pm

Rubus_chiliadenus · November 29, 2025, 6:15pm

It is not a good idea, because you have to choose a very high frequency to handle connection requests otherwise Jami will not receive any message.

Rubus_chiliadenus · December 3, 2025, 1:23pm

It’s merged, but dhtproxy2.jami.net didn’t send content_encoding header.

hazematman · December 3, 2025, 9:49pm

I don’t know for sure but I suspect the official proxies aren’t running the update yet. The latest v3.6.0 release doesn’t include the fix Release v3.6.0 · savoirfairelinux/opendht · GitHub