DEV Community

Discussion on: Self-hosted Jitsi server with authentication

Collapse
 
noandrea profile image
Andrea Giacobino

that looks like a DNS error, if you have set-up correctly the DNS to point to your server, it might take some time (few hours) for it the DNS record to propagate.

Collapse
 
jibsil profile image
JIBSIL

Strange. I use Cloudflare for my DNS and the “A” record has been set for a few days. Also, when I go to the IP of my Jitsi server, it says the same thing.

Thread Thread
 
noandrea profile image
Andrea Giacobino

I see. It is difficult to guess in the dark what could be the problem, the meaning of ERR_CONNECTION_REFUSED suggests that there is nothing responding on that server.
As for the why you will have to dig a bit deeper.
The tutorial is made to work on a ubuntu 18.04 image from a Hetzner server, and all the steps are required to get it done, if you are on a different platform or have skipped some steps it might not work.

Thread Thread
 
jibsil profile image
JIBSIL

Hmm... I've installed non-secure-domain (On a different VM on the same dedicated host) Jitsi Meet and it worked on the same domain with the same DNS records. I'm selfhosting from my own server on ubuntu 18.04. I don't think I skipped any steps... I'll try it again just to be safe

Thread Thread
 
jibsil profile image
JIBSIL • Edited

Update: I got Prosody working after I switched hypervisors... just don't know what's wrong with it.
Update 2: Jitsi is working, but without authentication. I can not enter a password to password-protect a room, which leads me to think that there is no permissions altogether (no moderator rights or admin-to-create-a-room things, I guess they are managed by Prosody?)