January 31Jan 31 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. 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.
January 31Jan 31 from what i see, the guide you were following is meant for a single-use server only for jitsi. May I suggest trying to use jitsi in a docker container, using non-standard http/https ports, and just use mod_proxy_http to Proxy from a froxlor-managed domain to the container? https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-docker/
January 31Jan 31 Author Ah, okay. thanks. I never worked with docker before and have to read through this. May take a while, but for what are weekends anyway.
February 28Feb 28 Hello Volatile, I'm using Froxlor and Jitsi. On Nginx I created a snippets which is included over Froxlor to the sub domain (Own SSL vHost-settings -> include /etc/nginx/snippets/jitsi.conf;). Jitsi was installed over apt only the domain was configured and no LetsEncrypt or anything. The rest will be done over Froxlor. I must say, I did this 2-3 Years ago. It is still working. So if you want to try it, I could send you the snippet over a PN. Parameter maybe need to be adjusted or updated. @d00p After testing I could also provide the file for others as well. Br, para-do-x
Create an account or sign in to comment