Secure connection?

Typically, I use Chrome. I don’t do anything special with it :slight_smile:
However, I tried using Firefox, and with ?secure=0 in the URL my PIN is accepted. So, using Chrome causes a rejection of my PIN when using ?secure=0, but Firefox does not

@jagauthier said:
Typically, I use Chrome. I don’t do anything special with it :slight_smile:

I use Chrome for Plex as well.
Have you tried to delete Chrome’s cache?

Deleting the cache actually did work. I created a new bookmark including ?secure=0 to work around the issue. It should do for now. Thanks for the help. Some strange things happening.

Hi. Here is my problem :

  • i have secure connection required
  • if i access my server remotely using https://plex.tv , everything is secure , all ok
  • if i access my server using https://myip:port , the browser is saying NOT SECURE , even if i still can access everything perfectly , i can start movies etc…
    Is this a bug or what ? Are direct ip access connections secure or not ?

@phenian said:

  • if i access my server using https://myip:port , the browser is saying NOT SECURE , even if i still can access everything perfectly , i can start movies etc…
    Is this a bug or what ? Are direct ip access connections secure or not ?

No, that is not a bug. The cryptographic certificate is “pinned” to the domain name that gets automatically assigned to your server.
If you access it with the local IP instead, the certificate is not valid. (a certificate cannot be pinned to a private IP address)
Hence the warning.

If you require secure connections, load the web app from plex.tv instead.
And don’t use Microsoft Edge in this case.

Verify also that you don’t have an issue with your router’s ‘DNS rebindig protection’:
https://forums.plex.tv/discussion/comment/1448011/#Comment_1448011

Thank you for answering. For certain reasons i want to access my server directly by ip/port . The server being set up on Required secure connection, how is the connection ? Secured or not ? Are direct ip access connections secure or not ?

@phenian said:
Thank you for answering. For certain reasons i want to access my server directly by ip/port . The server being set up on Required secure connection, how is the connection ? Secured or not ? Are direct ip access connections secure or not ?

Why exactly? Plex already know your IP when you turned on remote access, what’s the reason for not using Plex Web? More secure than direct to IP.

@phenian said:
Thank you for answering. For certain reasons i want to access my server directly by ip/port .

All clients are accessing the server directly.
What you are referring to is perhaps the URL from which you load the web app.
And this makes zero difference whether you load it from your own server or from plex.tv.
These are different things:

  1. The web app is loaded into the browser.
  2. the web app communicates with the plex server.

No matter from where the web app is loaded in step 1, it communicates always directly with your server.

Plex.tv by default gives your server a fully qualified domain name on the *.plex.direct domain. And it provides a cryptographic certificate, just for your server which is ‘pinned’ to this domain name.
Read more about it here: https://support.plex.tv/hc/en-us/articles/206225077-How-to-Use-Secure-Server-Connections

The server being set up on Required secure connection, how is the connection ? Secured or not ? Are direct ip access connections secure or not ?

If you insist on using a IP address or your custom domain name, it can only be secured, if you have a fitting cryptographic certificate. This certificate must be “pinned” to your IP/domain name. Otherwise it is rejected by the clients. And of course this certificate must be ‘trusted’ by the client devices.
If you don’t have such a certificate, depending on the setting ‘Secure Connections’ this means either:
(Disabled)+(Preferred) = no encryption/unsecured
(Required) = no connection to the clients

In case this is useful to others, I had issues getting remote secure access to function when connecting to https://app.plex.tv/desktop/

It turned out I was doing it to myself. Chrome addon uMatrix allows very granular control of whats allowed to load on a page. https://app.plex.tv/desktop/ requires plex.direct to be whitelisted.

Allowing that subdomain in uMatrix unblocked the secure load for me.