Christian Ulrich

dmesg doesn't say anything and it's not OOM (I checked the memory consumption with htop). To me it looks like uwsgi kills its worker process because klaus didn't respond within...

nginx has this in its logs ``` 2018/11/12 09:31:24 [error] 16565#16565: *3177 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 2a02:2450:102a:c75:1560:e24f:71fa:d25e, server: mydomain.com, request:...

> Are you sure you're using dulwich 0.19.6? That message is gone in 0.19.6. That's what my package manager (nix) says. The [package definition](https://github.com/NixOS/nixpkgs/blob/release-18.09/pkgs/development/python-modules/dulwich/default.nix) says, it's using 0.19.6 from Pypi.

I merged [a fix](https://github.com/weiss/mod_push/commit/04a29fb0d6b5e4040d680df9b30d8baa15aeca08) yesterday, did you pull that? The enable stanza should look similar to this: ``` xml http://jabber.org/protocol/pubsub#publish-options eruio234vzxc2kla-91 ``` There are examples in XEP-0357.

And yes, it should work with the sandbox server, actually it _only_ works with the sandbox server currently ;-) @robobit, I saw you implemented a sandbox config option. I should...

at a first glance I'm seeing you set "example.com" as register host, but are trying to register at "push.example.com"

Please set loglevel to 3 or higher in your ejabberd config and look for [error] and [warning] messages in your log file.

The existing backends could simply log the notifications before sending them. But I suppose your idea is to prevent connections to the vendor's push service before having configured credentials (e.g....

a mod_push_dummy backend shouldn't be much work, I put it on my todo list. Currently invalid credentials or tokens don't have any side effects (in the future I'm planning to...

You need to set jid='push.example.com' in the enable request. Push notifications are sent only when a client is in stream management's 'waiting for resumption' state (aka zombie state). Mobile clients...