XMPP Service Operators - 2023-09-17

Hello

array, if you have a question, just ask it

creep.im advertises xmpps-server on port 5269 with the same priority and port as starttls. But it doesn't work. That could lead to problems I think. Anyone here from creep.im?

Hmm… > !contact creep.im resulted in: forbidden

But the admin was hiding behind a captcha anyway and didn't read emails so they are hard to contact.

> array, if you have a question, just ask it i had one but i managed to resolve my issue thanks tho

Hey, what is port 5347 used for? Apparently Prosody uses this for the conference subdomain/component

Is that normal?

Or should I switch it back to the normal s2s port?

you probably should not have 5347 open, that is for other components like eg. biboumi

prosody will only listen for it on localhost to be safe by default iirc

Oh, well I cannot access any MUC so I thought I had to open port 5347

But on my friend's localhost (the server host) it works fine

5269 is for s2s access

regular s2s seems to work, but I just can't access the MUC component through s2s

It says Remote server not found

what happens if you try and manually do a dns lookup?

works good

It's a cname record

Okay I found something weird in my domain registrar's control panel

If you can't find it, your friend set something up wrongly

Wait, you can't access any muc? Then it is your server of course.. Your certificate or your dns records I bet

Again never mind, you can reach other servers but not their mucs, never heard of that. Should be technically the same. If you share your address I could do some tests

Okay so here's my DNS configuration in OVH, what's wrong here? https://cdn2.nuegia.net/4c38f716-779f-437c-bb32-90cbdfa943ae/dns_shenanigans_xmpp.png

Well, only you can read the addresses there, if it is out of zone or not... Double check I guess...

» [22:32:43] <Menel> Well, only you can read the addresses there, if it is out of zone or not... Double check I guess... I only blanked out the domain.tld

You can come up with conclusions just as well as I can

And I don't know what's wroing

Do you know what's wrong?

all the blanked out info except the A record value is the same domain.tld

you did rename the muc component to muc.xxxx right

on the prosody side

But what is this warning banner at the top?

What did I do wrong?

This is what the Prosody documentation told me to do

Is prosody's default to make the muc component muc.domain.tld?

I thought like ejabberd the default was conference.domain.tld

Just curious if it could be other things

It's not the default but it's the one I want

It appears that the error means that for the SRV record you made for the MUC, what it points at is 1. out of zone and 2. has no records on it

You blocked it out so we can't tell but it could be misspelled?

> It's not the default but it's the one I want You might need to change the prosody configuration so that the MUC component runs in that domain ↺

Already done. Funnily enough, on my friend's localhost it seems to work fine

So that makes me think it is a DNS issue

» [22:57:14] <unix.dog> You blocked it out so we can't tell but it could be misspelled? Wow you're right

lmao

lol

Hopefully it works now

gotta wait for propagation

MORE MONEY REQUIRED