My YunoHost server
Hardware: Raspberry Pi at home
YunoHost version: 4.2.6
I have access to my server : Through SSH
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : / yes
If yes, please explain:
changed .noho.st domain and moved converse app to im.personal.domain.tdl
Description of my issue
xmpp and converse app both worked fine (almost, because I had problem with xmpp-upload with my own domain, but worked fine with .noho.st domain) but I changed .noho.st domain recently and moved converse app to a personal subdomain.
I think this converse app moved is NOT the problem because using external clients (conversations android app) I can’t not log in either.
So I guess some nginx & metronome & dnsmasq missconfiguration is happening.
I did not manually change any file, but in browser console (F12) it fails to connect because of CORS policy (cross origin resource)
--force yunohost tools regen-conf for nginx and dnsmasq and metronome, and have reviewed logs but I’m not savvy enough to see there any valuable info
I have another app/services (nextcloud, wiki, …) all working fine (AFAIK).
Browser console message is similar to this (example):
just changing my domains on ynh
I’ve read I need to manually allow this on my server, but I guess if this was working fine until recent changes then it should also work if I force configuration reset on those services… unless I reconfiguring (forced) the wrong services.
Please would anyone suggest any hint and try to solve it? I can’t use xmpp with my server right now with any client and or account I’ve tried.
edit: I’ve a valid letsencrypt certificate for all involved domains (as seen in webadmin and browser)
ynh.domain.tld is my main domain (sso portal), users (email@example.com) can log in xmpp server.
users using “user1@my_ynh.noho.st” (firstname.lastname@example.org either) can’t log in.
im.domain.tld is where conversejs app is installed
Few days ago, before moving conversejs do new domain, I could log in with any of the users, and because email@example.com could use xmpp-upload withou issues then there was no problem, but now I can not use this login.
If I were able to solve xmpp-upload issue with ynh.domain.tld this would be a minor problem for my relatives