XMPP Service Operators - 2026-01-14

> I'm doing my part! Seems I have to reload the module again after my recent reboot. 🙄

> If you run an XMPP server and are willing and able, please consider registering it with the XMPP network graph at https://xmppnetwork.goodbytes.im/ Guus: i have pubsub and that module and it doesnt seem to accept my server

it says that i dont have PubSub Server Information, i added it to the modules

am i suposed to do some extra configuration besides having pubsub and the module enabled?

based.pt I'll have a look after lunch! Does your domain advertise DNS records for the pubsub domain?

it has a srv record

Seems that you're running Prosody. Your server is not advertising the server feature that's added by the module.

It's possibly not installed correctly?

ye possibly

i added it only to the pubsub component

A common issue with the prosody module is that you need to the XMPP domain itself (so, `based.pt`) needs to be made an admin of the pub/sub service. This is documented in https://modules.prosody.im/mod_pubsub_serverinfo.html but many people seem to think this needs to be a user account (e.g. `admin@based.pt`).

oh

i thought it needed to be someone in the domain

ill change that, thank you

ok, i changed it to the domain

still doesnt seem to work

Stuffing food in mouth, will look later

ill keep trying, might've missed something

eat well

I am having the same issue. I guess it might need a server restart?

why?

like, restart my machine?

Xmpp server I mean

I don't know if a restart is needed for Prosody to successfully load this module.

based.pt still does not advertise support for the feature.

Kris, what's your domain?

Joinjabber.org

i allways restart prosody when installing a module

Ok, I only reloaded it and thought that might be the problem.

joinjabber.org does not advertise the server feature either.

Is there anything in the server logs maybe?

we must be missing something obvious

nothing in logs

Are you using Prosody 13 or later? There's a conflicting module in 12

Latest prosody 13 here

13.0.2

That should be fine. Errr... I'm not sure how to diagnose this issue, apart from generic "lets look at the logs" and "did you read the instructions carefully" :-/

MattJ, are you available for insights?

well lets go over it step by step... i put the module loaded under the pubsub and i have the "admins" as the domain

Enable this module in the global or a virtual host.

I think that means it should go in the pubsub module?

The module requires a pubsub module to be present, but it should be installed in the global one

I put it in the global list

(and you configure the module to tell which pubsub module to use)

I think that the 'admins' configuration _does_ go in the pubsub module. `admins = { "joinjabber.org" }` respectively `admins = { "based.pt" }`

i used to have it like that but it didnt work

i changed it now

You're telling the global domain to _use_ the pubsub module, and you're configurating the pubsub module to accept the global domain as an admin.

And put "joinjabber.org" as and admin. But maybe that is the issue as we have the unusual setup of "joinjabber.org" being the MUC component. ✏

my muc is diferent

We have pubsub.joinjabber.org working so I assumed the default would be ok. Maybe I need to make that explicit 🤔

i never used pubsub so i dont really know

Is there a way to bump up the log verbosity and reload the module? You'd expect some kind of message being logged, right?

found it

the module didnt load

The obvious question being: why?

Domain 'based.pt' does support the serverinfo feature. It does explicitly define a pubsub-node on which info is published. 0 items are published on the node at: xmpp:pubsub.based.pt?;node=serverinfo

something changed :)

weird

it loads now but theres still an issue

it says "attempt to index a nil value (value 'metric_registry')"

oh it apears on the graph now

its only connected to igniterealtime.org

You are advertising support, so your server allows others to name you. My tests cause a connection from ignite to you.

You're not advertising your own connections though.

(probably because of that error)

hmm

I don't know what 'metric_registry' is - does that show up in your config?

But what was the original issue that you addressed? How did you make the module load?

> But what was the original issue that you addressed? How did you make the module load? it was missing another module

> I don't know what 'metric_registry' is - does that show up in your config? no

which one?

measure_active_users

I was unaware that this is a requirement. How did you figure this out?

logs

i wasnt figuring this out before because the logs dont save, i have to see them in real time

> measure_active_users Hmm, probably also not enabled here, need to check. ↺

its only requirement if you advertise active users

"Enabling this option will automatically load mod_measure_active_users." says the documentation. Is that a lie?

it might load, but if you dont have it installed it wont

ah.

Hmm, related question: does it even make sense to do all this if the server is only a MUC host with no active local users?

I think you can disable the usercounts, but the module itself lists the server-to-server connections, so that'd still be useful.

I do not know how prosody weight those usercounts though

I have added a 'common config issues' section to the readme at https://modules.prosody.im/mod_pubsub_serverinfo.html which hopefully helps the next poor soul.

based.pt: the only reference that I can see in the code to 'metrics' is when the usercount is enabled. Maybe disable that, to see if the error goes away?

user counts are currently not rendered by the website anyway.

ok

Guus: maybe `pubsub_serverinfo_publish_user_count = true` should default to false then?

It does

Hmm, then I still don't understand why it isn't working here 🤔

Kris: no argumente here. I'm a Java developer. Although lua is slightly more accessible than Erlang, it still is all Chinese to me. :)

Kris: no errors in your logs?

or maybe less verbose messages, when you restart the module?

I am currently not at my PC, but yesterday when I tried setting it up there was nothing in the default level logs.

``` local include_user_count = module:get_option_boolean(module.name.."_publish_user_count", false); ``` Seems to default to 'false'

Ah, sorry, I thought you were busy reconfiguring things Kris.

based.pt: something changed. You're now publishing data, as expected.

ye i disabled that

Hmm, that seems to be new: > Jan 14 20:18:50 mdosch.de:pubsub_serverinfo warn Failed to fetch/decode provider list: error<cancel:undefined-condition:> > Jan 14 20:18:50 diebesban.de:pubsub_serverinfo warn Failed to fetch/decode provider list: error<cancel:undefined-condition:>

Martin: I think that is your server complaining that it cannot fetch the content of https://data.xmpp.net/providers/v2/providers-Ds.json

it is accessible to me right now.

OK, then that's probably not the reason why I don't appear on the graph.

Ok, a restart helped.

> back when I installed this XMPP server it was considered legacy directtls was legacy? i was under the impression it was the other way around lol ↺

yeah, funny how these things change over time

> I am currently not at my PC, but yesterday when I tried setting it up there was nothing in the default level logs. I now explicitly configured the pubsub note, explicity disabled the user count and restarted the prosody server, but no difference ↺

nothing in the normal logs either

and and just for good measure I installed that optional module even though I am not using it

I am starting to think something just doesn't work when the root domain is not a vhost but a muc component

>> back when I installed this XMPP server it was considered legacy > directtls was legacy? i was under the impression it was the other way around lol in the dark ages of 2002 ietf thought plaintext would be fine forever and didn't want to "run out of ports" so all protocols standardized then shared a port and did their own starttls negotiation fast forward 12 years and 100% of protocols go over TLS on port 443, multiplexed with alpn... ↺

mandatory upgrade is standard for STARTLS these days, however there is a minor amount of metadata leak with STARTLS, so technically directls is better...

Guus, I was looking at my server logs and I see you aggressively close connections at xmppnetwork.goodbytes.im, one minute after it’s been established, yet the default delay between publishes is three minutes so we reestablish the connection then.

This seems very wasteful, whereas keeping a connection idle for two minutes is nothing.

I have a flood of those in my logs: Jan 14 23:56:55 s2sout3746580 info Stream encrypted (TLSv1.3 with TLS_AES_256_GCM_SHA384) Jan 14 23:56:55 s2sout3746580 info Outgoing s2s connection pubsub.linkmauve.fr->xmppnetwork.goodbytes.im complete Jan 14 23:57:04 s2sin2f828e0 info Incoming s2s stream conference.igniterealtime.org->linkmauve.fr closed: connection-timeout (Connection has been idle.) ✏

Kris [22:10]: > I am starting to think something just doesn't work when the root domain is not a vhost but a muc component Ah, you probably just need to load it on the component. Prosody has no concept of a "root domain" fwiw. But if you only added the module to the global modules_enabled, it won't be loaded on the component. https://prosody.im/doc/components - "Adding additional modules to an internal component"