JITSI DOCKER NGINX VERIFICATION
I guess if this is ran with sh -x a verbose output is given and it will probably show where the certificate verification is taking place. But before it’s placed there, there is a generation process, that’s happening somewhere else. So when that variable is expanded it would be /config/acme-certs/. This is where the cert is installed: docker-jitsi-meet/ssl.conf at d6fac8e0c38294463a535442bba3dd27327b966c This is the repo of the Jitsi Docker solution: GitHub - jitsi/docker-jitsi-meet: Jitsi Meet on Docker
JITSI DOCKER NGINX UPDATE
Anyone from the willing to have a look? If not, then I’ll now and then update this topic and people can always jump in with comments and feedback I can manually update Let’s Encrypt, no biggy. Resources needed or already arranged: The only thing that’s needed is time, which I have to prioritize to other things at the moment. Depending on how familiar someone is with this, I suspect this might be an afternoon of discovering the mechanisms and find a solution. The goal of this topic is to find this location so that I can bind it to the Docker host location of Nginx.
Your personal background within the context of the project: Senior Linux system and network engineerĮstimated timeline in terms of time boxed deliverables: I checked already briefly a month ago and couldn’t quickly find the location Jitsi uses for ACME. Now it doesn’t, because Nginx steals the request from Jitsi, so it never gets the data to finalize the ACME process.
The only thing I need to do is to bind the well-known ACME environment on the Docker host with the Jitsi ACME environment, so that it’s transparently shared and simply works. Jitsi has its own mechanism to update this. This proxy also handles the certificate regeneration of Discourse (the forum). However, due to Docker limitations, also with IPv6, I’ve put the forum behind an Nginx reverse proxy. This instance runs in Docker, which is easy to update and maintain in conjunction with Ansible. Project description (max 200 words): We are running our own Jitsi instance.
0 kommentar(er)
