I have a problem accessing the newly installed Jitsi (conferencing).
What I did: Jitsi is installed via APT into the system, not a customer, and an A entry to the DNS has been made, pointing to the (sub)domain which should deliver the GUI, something like: meetings.my-domain.com. After installation, one is asked to provide this name by the installer, and a set of configuration files, including LetsEncrypt stuff in generated, i.e. (probably more)
/etc/sysctl.d/20-jvb-udp-buffers.conf
/etc/sysctl.d/50-IPv6.conf
/usr/lib/sysctl.d/50-pid-max.conf
/etc/sysctl.d/99-nc-kernel.conf
/usr/lib/sysctl.d/99-protect-links.conf
/etc/sysctl.d/99-sysctl.conf
/etc/sysctl.conf
Now, when I open meetings.my-domain.com, I get however the Froxlor default "this domain is not configured" page. So I created the subdomain in the admin panel, but now I get of course the index.html of the resp. folder.
I guess, I have to change a virtual host file, so Froxlor doesn't deliver the "not configured" page, but I don't know which file exactly and how to do it properly so it doesn't get overridden by Froxlor the next time I (re)configure something.
I didn't do the optional FQDN step, because i wasn't sure if this breaks Froxlor or anything else, and I didn't secure the domain yet, but this only prevents anyone from create a conf. room, which isn't the issue atm.
So, If anyone maybe installed Jitsi before or knows what to do, any help would be appreciated. Thanks.
Question
Volatile
I have a problem accessing the newly installed Jitsi (conferencing).
What I did: Jitsi is installed via APT into the system, not a customer, and an A entry to the DNS has been made, pointing to the (sub)domain which should deliver the GUI, something like: meetings.my-domain.com. After installation, one is asked to provide this name by the installer, and a set of configuration files, including LetsEncrypt stuff in generated, i.e. (probably more)
Now, when I open meetings.my-domain.com, I get however the Froxlor default "this domain is not configured" page. So I created the subdomain in the admin panel, but now I get of course the index.html of the resp. folder.
I guess, I have to change a virtual host file, so Froxlor doesn't deliver the "not configured" page, but I don't know which file exactly and how to do it properly so it doesn't get overridden by Froxlor the next time I (re)configure something.
Additional Info: This is the quickstart of steps, in case someone needs to know: https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart/
I didn't do the optional FQDN step, because i wasn't sure if this breaks Froxlor or anything else, and I didn't secure the domain yet, but this only prevents anyone from create a conf. room, which isn't the issue atm.
So, If anyone maybe installed Jitsi before or knows what to do, any help would be appreciated. Thanks.
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now