Closed ageis closed 7 years ago
Hey @ageis - what version of jitsi-meet
does your box report? I noticed we are on an unstable branch - Been debating if we should jump onto the stable repo.
Also we've been utilizing the (jdauphant/ansible-role-nginx)[https://github.com/jdauphant/ansible-role-nginx] everywhere for nginx config. If we are experiencing any nginx issues on recent packages here, I do think this presents a good excuse to add that role as a galaxy dependency and rip out the custom nginx logic we have here.
I noticed we are on an unstable branch - Been debating if we should jump onto the stable repo.
Had a feature branch lying around that implemented stable repos, that's in #27 now.
@msheiny I am now on stable 1.0.1338-1.
I will mention that something weird happened a week ago and the config.js got totally wiped out. Must have been unattended upgrades of the unstable package? I dunno... Like I said, haven't had a chance to dig deep. But I do think the whole role should be re-tested cause I suspect there might be breaking changes happening upstream.
I will mention that something weird happened a week ago and the config.js got totally wiped out.
Anecdotal, but I also observed this on a personal meet machine a few weeks ago—also running unstable. Will move that box to stable branch once #27 lands and monitor over time.
No problems since switching from unstable to stable repo. Chalking this up to "unstable repo is unstable."
This task failed for me, as nginx was not installed via the jitsi-meet package for some reason
Not sure why, as it is listed in depends.
Installed it manually to get the task to succeed, but found that jitsi-videobridge was already bound to port 443.
Got nginx running by killing that, now jvb is only bound to UDP 10000+23347. Things seem to work, so I haven't done any further digging on what changed or why this occurred. There is this though: