Sönke Brightside

Setting PUBLIC_URL helps to solve the reconnect issue. But still Jitsi is not working properly and I have no clue why. The video bridge is somehow not working. JS Console:...

@bjoernbusch Hm. What if I don't have any root domain certificate? I have only the certs for the subdomains generated by letsencrypt.

Yeah okay. But this sounds like a bad workaround :-| Right now I think your first solution (default section for 443) looks the most promising.

Same for me. After upgrading to the latest release I get 404 for my assets. ``` - PENPOT_FLAGS=enable-login-with-password disable-email-verification enable-smtp enable-login-with-oidc disable-registration - PENPOT_SECRET_KEY=key - PENPOT_PUBLIC_URI=https://ux.example.de - PENPOT_DATABASE_URI=postgresql://penpot-postgres/penpot - PENPOT_DATABASE_USERNAME=penpot...

``` volumes: - /home/user/docker/volumes/penpot/assets:/opt/data/assets ``` Looks like the default path for the assets was changed. And since the nginx config doesn't care about PENPOT_STORAGE_ASSETS_FS_DIRECTORY we will get a 404. nginx...

You are right. The change was added at Jan 20, 2023 for the 1.17.0 release. Unfortunately we don't see what version you are using.

I've created a Pull-Request https://github.com/mbilozub/fpv_custom_mods/pull/19 for RC-1.

I don't think thats a good solution. I have a local repo where I can merge new versions of Betaflight. Every now and then I will try to create some...

Please try the original FW. I don't see any reason why those DJI workaround changes does affect those commands.

Added RC2. No compile errors on my side :)