Which version of jitsi-meet do you use? Do you have any modifications?
I see in the latest stable release the file jitsilogo.png is available in /usr/share/jitsi-meet/images/.
2023/04/09 16:33:44 [error] 517#517: *518 open() “/usr/share/jitsi-meet/images/jitsilogo.png?v=1” failed (2: No such file or directory), client: xx, server: jitsi.example.org, request: “GET /images%2Fjitsilogo.png%3Fv%3D1 HTTP/1.1”, host: “jitsi.example.org”
Not sure what is “pulling” that right now, as I am NOT connected to my instance, seems some webbrowser request in an open tab or the open electron
When logging in via electron to my instance (login screen) the “known issue” (/usr/share/jitsi-meet/lang/languages-de.json No such file or directory) pops in, will see if I can force the jitsilog.png error …
Calling the start page of my instance gives the following entries:
2023/04/09 17:05:31 [error] 517#517: *540 open() “/usr/share/jitsi-meet/images/deep-linking-image.png” failed (2: No such file or directory), client: 99.99.99, server: jitsi.example.org, request: “GET /images/deep-linking-image.png HTTP/1.1”, host: “jitsi.example.org”
2023/04/09 17:05:31 [error] 517#517: *535 open() “/usr/share/jitsi-meet/lang/languages-de.json” failed (2: No such file or directory), client: 99.99.99, server: jitsi.example.org, request: “GET /lang/languages-de.json HTTP/1.1”, host: “jitsi.example.org”, referrer: “https://jitsi.example.org/”
2023/04/09 17:05:31 [error] 517#517: *544 open() “/usr/share/jitsi-meet/lang/translation-languages-de.json” failed (2: No such file or directory), client: 99.99.99, server: jitsi.example.org, request: “GET /lang/translation-languages-de.json HTTP/1.1”, host: “jitsi.example.org”, referrer: “https://jitsi.example.org/”
so then just ignoring (as only I might be affected :)) or will it be checked by the jitsi team if in standard it is also throwing nginx error despite being there?
This I cannot repro. It must be something specific to your deployment, not sure what.
The language files is a ok known thing and we will address it at some point, it does not break anything so its not high priority for now.
None of these affects normal operating ofnthe deployment so ignore them.