Also tried and still failing. Perhaps something to do with Big Sur itself?
May I see the DEBUG logs ZIP file please which capture PMS starting?
I assume you want the logs for when encryption is set to required?
I am looking for the logs which capture PMS starting up .
Iām interested in seeing that initial exchange between PMS and Plex.tv where the certificate should be retrieved (for the SSL) but isnāt
@ChunckPa would you give me a hand, after the password change and after having claimed the server I no longer have secure connections, the only way is to delete the Preference.xml file but I lose all the history and settings. Looks like my server id got stuck. is it possible to reset this setting? or if I change a character in the id what happens?
Here are the logs.
I set the encryption to Required, then restarted. I tried to connect then from my iPad, but it didnāt work.
Plex Media Server.log (75.4 KB)
We can override whatās in Preferences.xml by adding the change to the end of the file (right before the closing />)
Not having secure conections inplies it doesnāt have a cerificate. Iāve looked at Plex.tv and it thinks the servers do.
I have sent you a PM of that I see. Please advise which server
Thank you very much,
I replied in PM.
I am not seeing any inbound connection requests at all.
With PMS stopped, would you please edit Preferences.xml
On the last line, right before the closing />, add secureConnections="1"
Now start PMS.
This is set for āPreferredā secure.
Letās see if it can go that far.
I have attached a new log with Preferred Encryption. I did not add it to the xml file as you suggested, rather via the interface.
I restarted PMS, then connected with my iPad. It is successfully displaying my content.Plex Media Server.log (105.2 KB)
Your logs are showing me HTTPS (which is what we want).
The only HTTP I see is where PMS is talking to itself (module->module) on 127.0.0.1.
This is all looking good to me.
How does it look to you?
Well⦠it works with the Preferred setting. However, I want it to work with Required. That is the problem.
Is there any way to further debug this or get to the root cause?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.