SSL Certificate Errors

I am getting this errors for the past week. Not sure where to start, tried what I know.
Please help! @ChuckPa

Oct 24, 2022 20:06:25.225 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42382 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:25.226 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42388 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:30.224 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42412 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:30.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42414 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:33.143 [0x154f2139cb38] WARN - Caught a system exception setting up WebSocket, ignoring.
Oct 24, 2022 20:06:35.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:54596 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:35.224 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:54598 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:40.233 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:54622 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:40.233 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:54628 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:45.229 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59232 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:45.232 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59236 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:50.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:59266 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:50.237 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59268 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:55.229 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:40650 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:06:55.230 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:40660 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:00.236 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:40686 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:00.236 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:40702 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:05.232 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:40088 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:05.232 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:40100 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:10.234 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:40122 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:10.234 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:40130 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:15.231 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59734 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:15.231 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:59748 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:20.230 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59774 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:20.230 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:59782 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:25.229 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:55190 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:25.229 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:55204 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:30.109 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:55234 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:30.109 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:55244 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:35.229 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42056 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:35.229 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42058 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:40.244 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42098 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:40.244 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42106 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:45.243 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38344 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:45.243 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:38360 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:50.136 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:38370 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:50.136 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38374 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:55.276 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:33242 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:07:55.276 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:33256 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:00.224 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:33276 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:00.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:33284 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:05.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:33034 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:05.224 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:33036 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:10.239 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:33074 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:10.239 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:33076 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:15.228 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:35136 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:15.228 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:35152 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:20.228 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:35170 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:20.228 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:35172 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:25.233 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38426 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:25.233 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:38436 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:30.230 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38462 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:30.230 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:38476 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:35.226 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36660 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:35.227 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:36672 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:40.231 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:36698 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:40.231 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36704 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:45.231 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:46326 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:45.232 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:46330 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:50.243 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:46344 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:50.243 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:46356 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:55.237 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:41108 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:08:55.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:41110 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:00.244 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:41138 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:00.244 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:41154 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:05.231 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:47186 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:05.231 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:47192 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:10.235 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:47204 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:10.235 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:47212 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:15.226 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:55858 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:15.226 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:55870 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:20.227 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:55886 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:20.227 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:55894 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:25.227 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53870 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:25.227 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53874 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:30.229 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53890 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:30.230 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53892 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:35.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:37868 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:35.238 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:37874 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:40.247 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:37886 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:40.248 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:37888 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:45.228 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:36324 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:45.228 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36328 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:50.234 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36356 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:50.234 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:36362 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:55.233 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42078 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:09:55.233 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42082 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:00.236 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42102 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:00.236 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42106 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:05.232 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:40542 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:05.232 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:40552 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:10.237 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:40586 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:10.238 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:40600 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:15.223 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42176 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:15.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42192 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:20.238 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:42226 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:20.239 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:42232 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:25.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:46084 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:25.238 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:46086 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:30.222 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:46116 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:30.223 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:46120 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:35.235 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53638 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:35.236 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53644 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:40.239 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53684 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:40.239 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53692 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:45.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:57116 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:45.237 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:57122 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:50.236 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:57132 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:50.236 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:57148 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:55.233 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:52614 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:10:55.233 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:52626 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:00.240 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:52660 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:00.240 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:52668 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:05.236 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:49164 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:05.239 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:49178 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:10.233 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:49214 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:10.235 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:49216 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:15.229 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38816 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:15.231 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38824 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:20.238 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:38848 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:20.239 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:38856 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:25.232 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:51564 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:25.234 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:51578 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:30.228 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:51596 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:30.228 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:51610 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:35.234 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:60964 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:35.234 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:60974 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:40.240 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:60990 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:40.240 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:32768 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:45.299 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:45816 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:45.300 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:45818 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:50.273 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:45860 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:50.274 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:45876 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:55.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:55344 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:11:55.225 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:55360 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:00.237 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:55392 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:00.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:55402 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:05.233 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36592 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:05.234 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:36606 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:10.241 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36632 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:10.241 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:36640 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:15.233 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:43376 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:15.234 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:43378 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:20.229 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:43394 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:20.229 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:43398 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:25.226 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:33816 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:25.227 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:33832 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:30.231 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:33870 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:30.231 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:33874 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:35.230 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53076 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:35.230 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53080 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:40.229 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53108 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:40.230 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53120 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:45.228 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:50870 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:45.229 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:50874 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:50.242 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:50896 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:12:50.243 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:50902 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:24.249 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36862 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:24.251 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:36878 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:31.881 [0x154f24727b38] WARN - [Req#5bb] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 24, 2022 20:13:31.881 [0x154f24727b38] WARN - [Req#5bb] QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
Oct 24, 2022 20:13:31.881 [0x154f24727b38] WARN - [Req#5bb] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 24, 2022 20:13:32.204 [0x154f2139cb38] WARN - [Req#5c3] QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
Oct 24, 2022 20:13:32.204 [0x154f2139cb38] WARN - [Req#5c3] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 24, 2022 20:13:32.204 [0x154f2139cb38] WARN - [Req#5c3] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 24, 2022 20:13:35.326 [0x154f234dfb38] WARN - [Req#5ce] QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
Oct 24, 2022 20:13:35.326 [0x154f234dfb38] WARN - [Req#5ce] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 24, 2022 20:13:35.326 [0x154f234dfb38] WARN - [Req#5ce] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 24, 2022 20:13:43.512 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59086 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:43.512 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:59102 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:45.223 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59118 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:45.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:59120 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:50.237 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:59146 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:50.237 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:59162 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:55.224 [0x154f26f30b38] WARN - [CERT] TLS connection from 192.168.0.4:53532 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert
Oct 24, 2022 20:13:55.224 [0x154f26d2db38] WARN - [CERT] TLS connection from 192.168.0.4:53540 came in with unrecognized plex.direct SNI name '192-168-0-4.9259b38ba53b472ca819940893bbcfd7.plex.direct'; using installed plex.direct cert

@enshittification

I have reset your certificate.

Before restarting, make certain file permissions are correct so the certificate can be written to the disk.

Restart the server

1 Like

@enshittification

Were you able to resolve it?

1 Like

I was about to reply, thanks for your help @ChuckPa . That seems to have resolved the issue of cert. Restarted the Server and looks fine. However there is a new error now which was not there before. I hope you have the solution for this one too.
Also, there is nothing being played in the background, the server just restarted.

:slightly_smiling_face: Thanks!

Oct 25, 2022 00:48:21.034 [0x148781facb38] WARN - [Req#97/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:48:51.082 [0x148781facb38] WARN - [Req#9f/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:49:21.110 [0x148781facb38] WARN - [Req#b3/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:49:51.150 [0x148781facb38] WARN - [Req#bc/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:50:21.188 [0x148781facb38] WARN - [Req#d4/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:50:51.224 [0x148781facb38] WARN - [Req#db/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:51:21.260 [0x148781facb38] WARN - [Req#e2/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:51:51.285 [0x148781facb38] WARN - [Req#e8/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:52:21.336 [0x148781facb38] WARN - [Req#ee/Transcode] Got a transcode session ping without a valid session ID.
Oct 25, 2022 00:52:51.377 [0x148781facb38] WARN - [Req#f3/Transcode] Got a transcode session ping without a valid session ID.

Restart the players so they all get the updated certificate as well

(clear everything cached because i did a hard reset)

Thanks for that, yes that is something I will have to do over the weekend being the only techie guy in the family lol.

Here is the current log right after boot.
Nvidia Shield on my network ip:192.168.0.40 is showing some error every few seconds in plex log even though Shield is off (sleep mode)

looks like some xml schema is missing or not formatted correctly.

Thanks!

Oct 25, 2022 17:22:38.008 [0x151fda686b38] INFO - Plex Media Server v1.29.1.6316-f4cdfea9c - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT -04:00
Oct 25, 2022 17:22:38.008 [0x151fda686b38] INFO - Linux version: 5.19.14-Unraid, language: en-US
Oct 25, 2022 17:22:38.008 [0x151fda686b38] INFO - Processor: 24-core       Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Oct 25, 2022 17:22:38.008 [0x151fda686b38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Oct 25, 2022 17:22:38.008 [0x151fda686b38] INFO - /usr/lib/plexmediaserver/Plex Media Server
Oct 25, 2022 17:22:38.023 [0x151fddf996f0] INFO - [CERT/OCSP] Successfully retrieved response from cache.
Oct 25, 2022 17:22:38.072 [0x151fddf996f0] INFO - Running migrations. (EPG 0)
Oct 25, 2022 17:22:38.176 [0x151fddf996f0] INFO - Running migrations. (EPG 0)
Oct 25, 2022 17:22:38.704 [0x151fd7c78b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Oct 25, 2022 17:22:38.704 [0x151fd7c78b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Oct 25, 2022 17:22:38.742 [0x151fd69c3b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Oct 25, 2022 17:22:38.742 [0x151fd69c3b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Oct 25, 2022 17:22:40.007 [0x151fd75e5b38] WARN - Crash: Crash reporting disabled
Oct 25, 2022 17:22:40.014 [0x151fd519fb38] INFO - Refreshing paths watched by LibraryUpdateManager
Oct 25, 2022 17:22:40.271 [0x151fddf996f0] WARN - [DatabaseFixups] Held transaction for too long (/data/jenkins/server/3535802588/Library/DatabaseFixups.cpp:378): 0.230000 seconds
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - XML: Entity: line 1:
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - XML: parser
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - XML: error :
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - XML: Start tag expected, '<' not found
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - XML: status=ok
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - XML: ^
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - Error parsing content.
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - Error parsing XML: Error parsing file.
Oct 25, 2022 17:22:40.312 [0x151fd3e40b38] ERROR - SSDP: Error parsing device schema for http://192.168.0.40:9080
Oct 25, 2022 17:22:40.701 [0x151fda225b38] WARN - [EventSourceClient/pubsub/172.105.13.59:443] MyPlex: attempted a reachability check but we're not yet mapped.
Oct 25, 2022 17:22:40.772 [0x151fd4449b38] INFO - Sync: downloaded 0 sync list(s) with 0 sync items(s): 0 new, 0 updated, 0 deleted
Oct 25, 2022 17:23:02.794 [0x151fd5db1b38] WARN - NAT: PMP, timed out waiting for response.
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - XML: Entity: line 1:
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - XML: parser
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - XML: error :
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - XML: Start tag expected, '<' not found
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - XML: status=ok
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - XML: ^
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - Error parsing content.
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - Error parsing XML: Error parsing file.
Oct 25, 2022 17:23:12.315 [0x151fd3e40b38] ERROR - SSDP: Error parsing device schema for http://192.168.0.40:9080
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - XML: Entity: line 1:
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - XML: parser
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - XML: error :
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - XML: Start tag expected, '<' not found
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - XML: status=ok
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - XML: ^
Oct 25, 2022 17:23:50.291 [0x151fd3e40b38] ERROR - Error parsing content.
Oct 25, 2022 17:23:50.292 [0x151fd3e40b38] ERROR - Error parsing XML: Error parsing file.
Oct 25, 2022 17:23:50.292 [0x151fd3e40b38] ERROR - SSDP: Error parsing device schema for http://192.168.0.40:9080
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - XML: Entity: line 1:
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - XML: parser
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - XML: error :
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - XML: Start tag expected, '<' not found
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - XML: status=ok
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - XML: ^
Oct 25, 2022 17:24:22.318 [0x151fd3e40b38] ERROR - Error parsing content.
Oct 25, 2022 17:24:22.319 [0x151fd3e40b38] ERROR - Error parsing XML: Error parsing file.
Oct 25, 2022 17:24:22.319 [0x151fd3e40b38] ERROR - SSDP: Error parsing device schema for http://192.168.0.40:9080
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - XML: Entity: line 1:
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - XML: parser
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - XML: error :
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - XML: Start tag expected, '<' not found
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - XML: status=ok
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - XML: ^
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - Error parsing content.
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - Error parsing XML: Error parsing file.
Oct 25, 2022 17:24:52.320 [0x151fd3e40b38] ERROR - SSDP: Error parsing device schema for http://192.168.0.40:9080

To me, looks like you need to edit Preferences.xml with PMS stopped and add LogDebug="1" before the /> on the closing line so we can see what’s really happening.

:wink:

Looks the same to me after adding LogDebug=“1”

 LogDebug="1"/>

>/plex/Library/Application Support/Plex Media Server/Logs# tail -f -n 100 Plex\ Media\ Server.log 
Oct 25, 2022 19:52:08.591 [0x14c870c74b38] INFO - Plex Media Server v1.29.1.6316-f4cdfea9c - Docker Docker Container (LinuxServer.io) x86_64 - build: linux-x86_64 debian - GMT -04:00
Oct 25, 2022 19:52:08.591 [0x14c870c74b38] INFO - Linux version: 5.19.14-Unraid, language: en-US
Oct 25, 2022 19:52:08.591 [0x14c870c74b38] INFO - Processor: 24-core       Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Oct 25, 2022 19:52:08.591 [0x14c870c74b38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Oct 25, 2022 19:52:08.591 [0x14c870c74b38] INFO - /usr/lib/plexmediaserver/Plex Media Server
Oct 25, 2022 19:52:08.606 [0x14c8745876f0] INFO - [CERT/OCSP] Successfully retrieved response from cache.
Oct 25, 2022 19:52:08.647 [0x14c8745876f0] INFO - Running migrations. (EPG 0)
Oct 25, 2022 19:52:08.749 [0x14c8745876f0] INFO - Running migrations. (EPG 0)
Oct 25, 2022 19:52:09.285 [0x14c86e266b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Oct 25, 2022 19:52:09.285 [0x14c86e266b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Oct 25, 2022 19:52:09.301 [0x14c86d1b4b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Oct 25, 2022 19:52:09.301 [0x14c86d1b4b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Oct 25, 2022 19:52:10.535 [0x14c86b78db38] INFO - Refreshing paths watched by LibraryUpdateManager
Oct 25, 2022 19:52:10.590 [0x14c86e508b38] WARN - Crash: Crash reporting disabled
Oct 25, 2022 19:52:10.770 [0x14c8745876f0] WARN - [DatabaseFixups] Held transaction for too long (/data/jenkins/server/3535802588/Library/DatabaseFixups.cpp:378): 0.240000 seconds
Oct 25, 2022 19:52:11.232 [0x14c870813b38] WARN - [EventSourceClient/pubsub/172.105.13.59:443] MyPlex: attempted a reachability check but we're not yet mapped.
Oct 25, 2022 19:52:11.311 [0x14c86a8c8b38] INFO - Sync: downloaded 0 sync list(s) with 0 sync items(s): 0 new, 0 updated, 0 deleted
Oct 25, 2022 19:52:19.106 [0x14c86acceb38] INFO - [Req#3a] AutoUpdate: no updates available
Oct 25, 2022 19:52:32.941 [0x14c86cdaeb38] WARN - NAT: PMP, timed out waiting for response.
Oct 25, 2022 19:52:38.989 [0x14c86acceb38] WARN - [Req#bd] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 25, 2022 19:52:38.989 [0x14c86acceb38] WARN - [Req#bd] QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
Oct 25, 2022 19:52:38.989 [0x14c86acceb38] WARN - [Req#bd] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 25, 2022 19:52:41.292 [0x14c8696adb38] WARN - [Req#d3] QueryParser: Invalid field 'libraryHubsOnly' found, ignoring.
Oct 25, 2022 19:52:41.292 [0x14c8696adb38] WARN - [Req#d3] QueryParser: Invalid field 'pinnedContentDirectoryID' found, ignoring.
Oct 25, 2022 19:52:41.292 [0x14c8696adb38] WARN - [Req#d3] QueryParser: Invalid field 'contentDirectoryID' found, ignoring.
Oct 25, 2022 19:52:50.557 [0x14c8696adb38] INFO - [Req#eb] AutoUpdate: no updates available
Oct 25, 2022 19:52:51.932 [0x14c86acceb38] WARN - [Req#10e] SLOW QUERY: It took 1460.000000 ms to retrieve 30 items.
Oct 25, 2022 19:52:57.307 [0x14c86acceb38] WARN - [Req#13e] SLOW QUERY: It took 1130.000000 ms to retrieve 30 items.
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - XML: Entity: line 1:
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - XML: parser
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - XML: error :
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - XML: Start tag expected, '<' not found
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - XML: status=ok
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - XML: ^
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - Error parsing content.
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - Error parsing XML: Error parsing file.
Oct 25, 2022 19:53:00.491 [0x14c86a2bfb38] ERROR - SSDP: Error parsing device schema for http://192.168.0.40:9080
Oct 25, 2022 19:53:08.319 [0x14c86acceb38] WARN - [Req#18e] SLOW QUERY: It took 1070.000000 ms to retrieve 30 items.

May I have the entire Log ZIP please of all the logs?

I can’t diagnose from a snippet.

Also, Please share your Preferences.xml but REDACT

  1. PlexOnlineUsername
  2. PlexOnlineMail
  3. PlexOnlineToken
  4. ALL UUID fields.

Thanks

It’s not possible for PMS to run for a fulll minute without generating DEBUG statements when enabled.

1 Like

Yeah, things are weird. Something is not right because that is the log I got last time. I am sharing the log after another restart now because I verified everything again. Also, I have not got that error yet. I am not sure what is up but I did expect few DEBUG statements.

The logs I have posted before are not snippets, they start right when the server starts upto the point the error is thrown. Nothing is skipped in between

Cheers!
Logs+Preferences.zip (3.7 KB)

I found it. LogDebug is a special case.

logDebug
1/0
Sets whether “debug” logging is enabled.
1

logDebug not LogDebug

:confused:

I know logNumFiles and LogNumFiles both work. Confusing.

I did that before you even asked, I checked that online because I was not seeing any DEBUG logs and when I used lower case “L” server crashes on startup with error. Only crash log is created so I deduced that Upper Case “L” is the way to go.
Let me do this and attach the crash log to this post in a few minutes to demonstrate.

Cheers!
Lowercase_L_Logs+Preferences.zip (1.3 KB)

Look in your preferences.xml file.

If you already have another logDebug="0" – change it to “1”.

PMS will crash if there is a duplicate.

1 Like

Checked this and you are correct there was 2 logDebug switches.
I will correct this and post again if there is any other issue.

Cheers!

Hi @ChuckPa

Thanks for your help and effort into diagnosing this.

So, I have concluded that the error is from Plex Scanning the network and looking for some xml-schema in the response. For Nvidia Shield request path is <LOCAL-IP>:9080, however sheild only sends back status=ok as response so plex throws that error. Server also scans other devices on the network and determines their type and looks for IGD=Internet Gateway Device.

I have debug logs, however it is too much work to sanitize them for public uploads. I will be happy to upload the initial 500 lines or so from boot to the error as I have posted here before if you want to have a look. Any logs files other than “Plex Media Server.log” do not have any reference of this.

Is there any way to stop plex from scanning my network, I already have “Enable local network discovery (GDM)” Turned Off in the Network Settings.

Cheers!

those SSDP errors can only be turned off in the individual devices themselves.

The problem is that most do not allow network discovery (what SSDP was created for) to be turned off.

While not an answer – Ignore the error messages for the SSDP queries.

It’s a PITA but when a manufacturer doesn’t adhere to standards – what can you do?

1 Like

I agree with you. Thanks for your time.

Cheers!

I have the same problem. Could you reset mine?

@pwrqwest

You have two servers on your account.

Both of which appear to have valid (not throttled status) certificates.

Which is giving you the issue and how does it manifest please ?

Thanks Chuck

I have the following in my Media service log file.

I have two servers .11 and 10.

Nov 23, 2022 11:26:32.437 [0x16fbbb000] WARN - [CERT] TLS connection from 172.16.0.10:60858 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:26:32.471 [0x16fbbb000] WARN - [CERT] TLS connection from 172.16.0.10:60860 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:27:02.494 [0x16fb2f000] WARN - [CERT] TLS connection from 172.16.0.10:48504 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:27:02.585 [0x16fbbb000] WARN - [CERT] TLS connection from 172.16.0.10:48518 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:27:32.610 [0x16fbbb000] WARN - [CERT] TLS connection from 172.16.0.10:49274 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:27:32.687 [0x16fbbb000] WARN - [CERT] TLS connection from 172.16.0.10:49276 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:28:02.712 [0x16fbbb000] WARN - [CERT] TLS connection from 172.16.0.10:45998 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:28:02.741 [0x16fb2f000] WARN - [CERT] TLS connection from 172.16.0.10:46004 came in with unrecognized plex.direct SNI name ‘172-16-0-11.548a0f…52786.plex.direct’; using installed plex.direct cert

Nov 23, 2022 11:28:17.359 [0x16fbbb000] WARN - [CERT] TLS connection from 107.72.98.60:4941 came in with unrecognized plex.direct SNI name ‘108-64-10-84.305bad7…3f94.plex.direct’; using installed plex.direct cert