You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Somewhat related to #51
I have plex set to SSL required, which kind of breaks Moviematch.
i do not have an external domain pointed towards plex nor do i use custom certificates.
plex creates real certificates (*.*.plex.direct) to allow communication securely through https://app.plex.tv
I prefer to use that instead of managing it myself.
Describe the solution you'd like
I would like if MovieMatch added config option for deno#11324 deno#1371 --unsafely-treat-insecure-origin-as-secure
this way i can use required ssl and https towards the IP like - PLEX_URL=https://192.168.1.10:32400
to allow further tinkering with flags in the future, could implement something like - DENO_FLAGS=--unsafely-treat-insecure-origin-as-secure,option2,option3
or just specifically this config option - PLEX_URL_ALLOW_INSECURE=YES
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Somewhat related to #51
I have plex set to SSL required, which kind of breaks Moviematch.
i do not have an external domain pointed towards plex nor do i use custom certificates.
plex creates real certificates (
*.*.plex.direct
) to allow communication securely through https://app.plex.tvI prefer to use that instead of managing it myself.
Describe the solution you'd like
I would like if MovieMatch added config option for
deno#11324
deno#1371
--unsafely-treat-insecure-origin-as-secure
this way i can use required ssl and https towards the IP like
- PLEX_URL=https://192.168.1.10:32400
to allow further tinkering with flags in the future, could implement something like
- DENO_FLAGS=--unsafely-treat-insecure-origin-as-secure,option2,option3
or just specifically this config option
- PLEX_URL_ALLOW_INSECURE=YES
The text was updated successfully, but these errors were encountered: