[BUG] Plex Require Secure Connections

[PhasecoreX]

Describe the bug
Plex set to require secure connections prevents WatchState from adding backend

To Reproduce

1. Log into app.plex.tv
2. Click the wrench at the top right
3. Go to -> settings -> network
4. Click "Show Advanced" button if not already clicked
5. Set "Secure connections" to "Required"
6. Attempt to add plex as a backend in WatchState

Expected behavior
Can add Plex as a backend

Basic report

[ Basic Report ]

WatchState version: v1.0.0
PHP version: cli/8.4.12
Timezone: UTC
Data path: /config
Temp path: /config
Database migrated?: Yes
Does the '.env' file exists? Yes
Is the tasks scheduler working? Yes 'Container' - Task scheduler is running.
Running in container? Yes
Report generated at: 2025-10-30T12:09:11+00:00

It's a brand new instance so I didn't include all the empty log files and such.

Additional context
When you tell Plex to require secure connections, it makes the 32400 port require https/tls. If you use http://, it will immediately drop the connection. The "add backend" section of WatchState will properly sign in and detect all of the URLs to connect, however it shows the bare IP address ones as "http://" (such as "http://10.0.0.7"). When it tries to connect it fails. So we need a way to force https, and also to ignore the certificate name not matching (I think it's a let's encrypt certificate with the plex.direct URL).

[arabcoders]

Hello,

The list are what plex reports to us, it's possible to disable ssl via options.client.verify_host = false in servers.yaml, however i'll add it to the extra options section.

Could you point to one of the plexdirect links and after that manually edit the servers.yaml to include the option i outlined than switch to the https://10.xxx address?

I'll update the plex connector to also include option for https://address.

Also, btw you can add external host to your plex config and it will show up in select server list.

[arabcoders]

This should be covered in v1.0.1

[PhasecoreX]

Apologies for the delay, I was at work. I added the backend with the plex direct link, then stopped the container and updated the servers.yaml with the updates you suggested. Starting the container again, I was able to run an import so I assume it works properly! Thank you!

[arabcoders]

Glad to hear it's working for you.

[PhasecoreX]

Apologies, I just got around to updating to 1.0.1 and testing this out properly. I unchecked the "Validate SSL Certificate" and I was able to get through all of the setup until clicking the "add backend" button. When clicked, it gives this error in the red banner at the top right:

Failed to Add backend. (400: Failed to connect to backend. SSL: no alternative certificate subject name matches target ipv4 address '10.0.0.7' for "https://10.0.0.7:32400/?pin=1234".).

(No, that's not my real pin)

Interestingly, when I have "Validate SSL Certificate" turned off, I can see my home users in the User dropdown, whereas when it is turned on, it only shows my account. So I assume that the toggle is doing something, just maybe it isn't taken into account when actually adding the backend.

[arabcoders]

Apologies, I just got around to updating to 1.0.1 and testing this out properly. I unchecked the "Validate SSL Certificate" and I was able to get through all of the setup until clicking the "add backend" button. When clicked, it gives this error in the red banner at the top right:

Failed to Add backend. (400: Failed to connect to backend. SSL: no alternative certificate subject name matches target ipv4 address '10.0.0.7' for "https://10.0.0.7:32400/?pin=1234".).

(No, that's not my real pin)

Interestingly, when I have "Validate SSL Certificate" turned off, I can see my home users in the User dropdown, whereas when it is turned on, it only shows my account. So I assume that the toggle is doing something, just maybe it isn't taken into account when actually adding the backend.

Unfortunately it was partially fixed in the release tag could you switch to :dev or :master and see if this completely fix your issue?

[PhasecoreX]

I tried both :dev and :master, both unfortunately give the same error above.

[arabcoders]

I tried both :dev and :master, both unfortunately give the same error above.

Thats really weird, i tested plex and jellyfin and all of them now accepts ignoring ssl warnings.

I am thinking it might be cache related can you try via new incognito window? mainly the dev tag as it has all recent changes.