Hi everyone!
Yesterday I wanted to configure my Plex server for connections outside of my own network.
As you can see Plex tells me that a Connection from outside was not possible. Thats the first strange thing because it works.
When I go to my Server via https://my.url.com:32400 Plex works and even the green lock apears.
But the problem my Browser (Firefox) says that the certificate was not secure.
I hope you can help me. How can I fix this?
@flow said:
So, simply don’t use your domain from myfritz.net use instead plex.tv, this will lead you to the correct domain, with correct ssl. Plex only issues ssl certs for your *.xxx.plex.direct domain to you, and not to your domain.
Thanks fpr your answer!
When I use plex.tv, no connection is possible. Any Ideas?
If you want to use your own url, you need to provide your own certificate.
You might generate a letsencrypt certificate for your dydns-fqdn (which exceeds after 90 days and needs to be renewed) and use it to create a PKCS#12 file, which can be used in plex.
Though, it’s actualy easer to just use https://app.plex.tv to access your instance.
@kopfpilot said:
Though, it’s actualy easer to just use https://app.plex.tv to access your instance.
I’m fine with using plex.tv but the server is not avalible there, no Idea why.
put the exception for the DNS rebinding protection into your router, as @flow mentioned above
Set the DNS server in your router to Google (8.8.8.8 and/or 8.8.4.4) or OpenDNS
DNS servers from ISPs often suck when it comes to resolving the .direct TLD (T-Offline, Kabel DE etc)
create a manual portforwarding
Don’t use reverse proxies or other networking tricks unless you know exactly what you are doing
put a checkmark into the box ’ Manually specify public port’ and put the external port number of your portforwarding behind it.
Don’t put anything into
‘Custom server access URLs’
‘Custom certificate location’
‘Custom certificate domain’
After doing all of the above, restart your devices
in this order, with a few minutes inbetween
Ignore the message ‘Not available outside your network’
for at least 30 minutes after server restart.
This one sometime takes a while until it reflects the real status quo.
@flow said:
So it might be the DNS Rebinding Protection of your FritzBox. Just add
plex.direct
I added “plex.direct”, but that didn’t solve the Problem.
@OttoKerner said:
2) Set the DNS server in your router to Google (8.8.8.8 and/or 8.8.4.4) or OpenDNS
I’m using 9.9.9.9 or alternatively 8.8.8.8
@OttoKerner said:
3) create a manual portforwarding
I did that
@OttoKerner said:
4) Don’t use reverse proxies or other networking tricks unless you know exactly what you are doing
As far as I know I’m not doing so.
@OttoKerner said:
5) put a checkmark into the box ’ Manually specify public port’ and put the external port number of your portforwarding behind it.
Check!
@OttoKerner said:
Don’t put anything into
‘Custom server access URLs’
‘Custom certificate location’
‘Custom certificate domain’
Check!
I already restarted my Router and will restart my Server when I’m at home. In the moment it doesn’t work.
I restarted everything and it didn’t change anything.
When at home use any computer behind your Fritz!Box to DNS resolve your server as in this example
host 192-168-1-6.28f57960021746b59464xxxxxxxxxxxxx.plex.direct
You get your lengthy string in the address string from looking at what the web interface generates as URL. The first part is derived from the local IP of your server. It should result in the local IP#, i.e. 192.168.1.6 in my example. Note the dashes replacing the periods.
Next, you do the same thing using a computer outside of your home network. The result should be your external IP#.
That will provide a clearer picture of your problem.
I think your port forwarding works just fine, as you can reach your server, when using the AVM/Fritz!Box indirect DNS service.
PS: I learned all that from Otto 
I am such an Idiot!!! I double checkt everything and didn’t see the typo.
Look at my first screenshot. I told Plex to forward to Port 32440 instead of Port 32400.
I changed that and now everything works fine. Post a facepalm gif
