Connecting with SSL doesn't work -- connecting without does

General Discussions
1

Hey.

So the title pretty much says it all.

I can connect both externally and internally, in every manner of way – plex.tv & localhost (from the same computer as the server is running and on other computers), PHT, Android app, etc.

But, only if I am not using secure connections (for the platforms that support it). As soon as I re-open, say, the plex.tv tab, I have to let it timeout and reload using insecure connections.

The server is set to Preferred as far as secure connections go, and the remote access status is green and shows the IP mappings correctly. PMS v0.9.16.5.

SSL isn’t vital to me, but I would like to have it if possible. Any ideas?

2

When you open your browser to plex.tv, open the developer tools. In both Firefox and Chrome, this can be quickly accomplished by right-clicking on the page background and select Inspect or Inspect Element. Go to the Network tab, and look for the requests to your server (you may have to reload the page after opening this tab for them to show up). They should end with plex.direct. Select those, and you should have some indication as to why the secure connections are failing.

3

Request URL:https://192-168-1-30.***************.plex.direct:32400/
Status: Failed

This is how it looks for lines and lines, interspersed with requests going to my external IP (that also fail, naturally).

Edit: And I guess I should add, there is no other information provided.

Edit 2: Attached screenshot. Hitting the tabs “Preview” and “Reponse” is just white pages with “Failed to load response data”

The IPs are correct:

1166×406 31.3 KB

4

Check the console as well, but my guess is that your router or DNS provider is refusing to resolve names in the 192.168.0.0/16 block. SSL connections do not work without these DNS entries resolving but non-SSL connections will.

5

Indeed, DNS rebinding was the problem!

I’m using pfSense and the accepted answer here did it.

6

@vsoraas said:
Indeed, DNS rebinding was the problem!

I’m using pfSense and the accepted answer here did it.

Thanks for fixing my router as well. Pfsense as well.