[FEAT] Enforcing trust in Chrome as an APP for this docker

[JaCh0o]

Is this a new feature request?

• I have searched the existing issues

Wanted change

Current default setting forces https in this docker which is ok - it uses self-signed cert whitch gives an error: net::ERR_CERT_COMMON_NAME_INVALID
adding cert to truted root authorities in windows or in chrome directly (chrome://certificate-manager/localcerts) does not resolve it while creating chrome app.
Is there any way to add certificate or somehow force trust to leit it work properly?

Reason for change

I would like to create possiblity to create an chrome app of this docker to use it as windows application.

Proposed code change

No response

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[thelamer]

Use a reverse proxy and a legit cert, I use duckdns and swag on my local network and have router level dns for the domain to local IP parsing, but there are many solutions.

https://github.com/linuxserver/docker-swag