Custom port for mod_unified_push

[stratself]

When hosting mod_unified_push behind a reverse proxy with traefik:443 --> ejabberd:5280 port mapping, registering an UP service will return a domain.name:5280 endpoint, which is unroutable. While this can be worked around with changing the http service port to 443 inside ejabberd, that would require the extra NET_BIND_SERVICE capability for the docker container.

Therefore, I suggest having an option to specify custom UP port, to conveniently handle these situations.

[badlop]

Right now the function guess_url_prefix/1 builds the uri string reading ejabberd configuration.

I guess you would want an option similar to mod_host_meta websocket_url, to allow you setting custom port, or any other custom URI, right?

[stratself]

Yes, that would be ideal thanks

[badlop]

You can try the new option and comment if it works as expected.

[DrDimedrol]

Can you provide some explanation how to configure plugin to use custom URL? I'm not familar with erlang.
I added following lines to ejabberd.yml,

modules:
  mod_unified_push:
    push_url: "xmpp.@HOST@"

but it didn't help me. I got push url like:
https://my.host:5443/up/push/....somerandomtext.
instead of https://xmpp.my.host/up/push/...

also push_url: "https://xmpp.my.host" and "xmpp.my.host/up" didn't help too.

[stratself]

Doesn't work for me either. I did reload_config without errors about unrecognized fields, so the update should be successful.

ejabberd.yaml relevant parts:

log_modules_fully: [ mod_unified_push ]

modules:
  mod_unified_push:
    push_url: "https://mydomain.com:443/up"

listen:
  -
    port: 5280
    module: ejabberd_http
    tls: true
    request_handlers:
      /up: mod_unified_push
      /ws: ejabberd_http_ws 

Module logs show the registration:

2025-12-02 06:37:45.543 [debug] processing unified push IQ: {:iq, "_FiOGuILvZAA", :set, "en",
 {:jid, "<user>", "<domain>", "<resource-name>", "<user>",
  "<domain>", "<resource-name>"},
 {:jid, "", "<domain>", "", "", "<domain>", ""},
 [
   {:unified_push_register, "7EsP9RjRzjD4xLeZAGqIiZOn7bQNxvh8GS7IhF6lBp0=",
    "WpOFUqdsa2D6taIG1tkkgQkjtU+TgdFMz4kTrHIxGgE="}
 ], %{ip: {192, 168, 1, 8}}}

But UP-Example still shows the endpoint as coming from :5280. Sending a notification obviously throws an error:

A2.i: java.net.ConnectException: Failed to connect to <domain>/192.168.1.40:5280

[badlop]

Ah, there was a bug and the code didn't work correctly in some cases. I've fixed it now, please try again.

---

Example configuration:

hosts:
  - example.org

listen:
  -
    port: 5443
    module: ejabberd_http
    tls: true
    request_handlers:
      /up: mod_unified_push

modules:
  mod_unified_push: {}

With that configuration, this is the URL used:

mod_unified_push:get_push_url(<<"example.org">>).
<<"https://example.org:5443/up/">>

---

In your case, as you want to setup a custom port number (or path, or whatever), then you must setup manually the URL:

modules:
  mod_unified_push:
    push_url: "https://xmpp.@HOST@:443/up/"

With that configuration, this is the URL used:

mod_unified_push:get_push_url(<<"example.org">>).
<<"https://xmpp.example.org:443/up">>

[stratself]

Uninstalled and reinstalled the module. It works as expected now, thanks