I don't think PLEX is connecting to plex.tv

dennypage

@jay_k Okay. My question isn't pertinent then and should be ignored.

johnpoz

@jay_k said in I don't think PLEX is connecting to plex.tv:

I'm not sure what Plex rebind protection is

rebind protection is when unbound resolves or forwards and the IP comes back as rfc1918 you wouldn't get an answer.

This can prevent connection to your local plex, because you don't get a response.. Unless you enable plex.direct to allow for rfc1918 responses - your local IP.

So for example..

with how ssl certs work with plex you would have your own special fqdn to get to yours and use the ssl they provide, etc. And this would return your rfc1918 address

If you do not have the rebind protection turned off for this then this would fail.

Now this doesn't seem related if you can not even resolve plex.tv, but you more than likely will want to set this up if you want to locally access your plex and not have to do a relay sort of connection to access when your on your own network, or nat reflection etc..

So from pfsense can you not resolve plex.tv

example

[22.05-RELEASE][admin@sg4860.local.lan]/root: dig plex.tv

; <<>> DiG 9.16.26 <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 19026
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                519     IN      A       52.31.221.232
plex.tv.                519     IN      A       54.154.55.122
plex.tv.                519     IN      A       54.229.236.47
plex.tv.                519     IN      A       52.212.151.244
plex.tv.                519     IN      A       52.212.166.170

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 08 09:59:09 CDT 2022
;; MSG SIZE  rcvd: 116

[22.05-RELEASE][admin@sg4860.local.lan]/root:

jay_k

@johnpoz, I did try to add plex.direct to the custom options in DNS Resolver a couple of times with no luck. I also ran dig plex.tv in pfSense shell and got a very similar output to yours. So maybe I am connecting to plex.tv? Sorry. Most of this is over my head.

johnpoz

@jay_k so what exactly is not working?

If you login to your plex from what - firestick, appletv, your browser, roku - does it not work?

I have been running plex behind pfsense for since forever I have had plex, and have had zero issues with any local clients, or any of my remote users - that are many, friend and family there are prob 40 some users accessing my plex server, etc..

So pretty sure we can help you work through whatever issues you might be seeing, just need some details.

dennypage

I don't have nearly as many friends & family accessing my Plex as @johnpoz does, which probably means that I just don't have that many friends...

johnpoz

@dennypage my problem is I have a hard time saying no, if was me it would 1/4 of that - some are friends of friends sort of access.

But I do enjoy making people happy.. so when a friend asks hey can X have access, and I met
X one time a year ago over beers I say sure.. Atleast they use it, others like family say hey can I have access - then they watch one thing, and then nothing for 8 months..

After the breech issue, I going to go through and delete anyone that hasn't watched anything in X months.. Screw um! ;)

jay_k

@johnpoz, First, I have a Samsung TV that can no longer access PLEX at all, but I'm hearing that the Samsung TVs running Tizen are having issues with this lately. So I'm not sure this issue needs to get added to the bag of fun just yet. Otherwise, I have 3 Rokus' that can all access Plex. However, now that I'm digging more into this, last night I started noticing playback errors that weren't there before. Both on the Roku and the web UI. The logs have me believing that this only happens when Plex needs to transcode... I think. I'm also finding that the Android app will still load my libraries, but when I try to open a show I get a connection error. And I still can't update metadata, which, until now, I thought was my only problem. As far as I know, Plex only allows you to update metadata through the web UI.

The playback errors gave me the idea that maybe I didn't give the Plex container enough storage space, then I couldn't add metadata or transcode, but that seems to be fine, there's still 12 Gb free.

2 CPUs
1 Gb RAM
16 Gb HDD

I also just noticed this morning that when I log in to the Plex container shell, I get this error;

"Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings"

No other container or virtual machine gives me this error on login.

I'm getting good and confused now. I "think" this is still an issue with pfSense. I'm also pouring through the Plex forums with no luck. Maybe my next move should be to switch back to the Night Hawk router just to confirm that everything works again. That's a pain though, and with my wife pretty much constantly streaming something, I need to make peace with god before taking down the internet. HA! I might try to tackle this over the weekend. If you don't hear from me again, I'm probably buried out in the field. lol

johnpoz

@jay_k said in I don't think PLEX is connecting to plex.tv:

I have a Samsung TV that can no longer access PLEX at all

Yeah believe that is do to some changes in the certs used for ssl, I believe a work around on plex is to allow for non secure connection. Not like I would suggest that - but believe its a possible work around.

I have 3 Rokus' that can all access Plex.

But if those are local and you didn't setup the plex.direct thing they could very well be using relay to get in, which could cause all sorts of problems with playback because it limited in bandwidth of only 1mbps, or 2 if your plex pass.

Using some soho router might out of the box do nat reflection, which would allow for the local connection without relay. Pfsense out of the box doesn't do nat reflection, etc. You would have to set it up, but better option is setting plex.direct as private.

stephenw10

Can you just try to resolve something fro the plex shell? I imagine it will fail, what error does it show?

jay_k

@stephenw10 I ran dig from the Plex shell and got

;; communications error to 10.0.0.1#53: connection refused

I went to try this in the other container Now when I log in, I'm getting the connection error I mentioned earlier. When run dig, I get the above error.

@johnpoz I added the plex.direct line to the custom options in DNS resolver. This didn't seem to change anything.

For what it's worth, I did another test today. I unplugged my WAN from pfSence, disconnecting my internet, and the Roku's still worked as the did with the internet connected.

stephenw10

10.0.0.1 is pfSense there? And that's the LAN subnet or a seperate subnet for the containers?

Something is blocking it though.

Steve

dennypage

@jay_k said in I don't think PLEX is connecting to plex.tv:

I also just noticed this morning that when I log in to the Plex container shell, I get this error;
"Failed to connect to https://changelogs.ubuntu.com/meta-release-lts. Check your Internet connection or proxy settings"

I would set Plex aside for the moment and work directly on basic network/dns troubleshooting.

I think it might help if you posted some basic configuration information for your pfSense install, including your network assignments (Interface name and addresses), and DNS configuration.

Also, some basic network/dns config for the VM you are running Plex in.

johnpoz

@dennypage said in I don't think PLEX is connecting to plex.tv:

config for the VM you are running Plex in.

Sounds more to me that he is running it in a docker, which is a very common setup for plex as of late. Some people think its an easier setup, and while sure it would allow for easy move of all of plex from one host to another, etc.

And I run some things in a docker container, I never saw the advantage of doing it for plex in my setup. I just install the native install on my nas.

I believe the containers normally default to a 172.16 or something network, and then there is natting that has to go on, would all depend on how exactly he has his networking setup for his docker containers.. But that for sure could be part of his problem if he can not talk to dns.

dennypage

@johnpoz said in I don't think PLEX is connecting to plex.tv:

Sounds more to me that he is running it in a docker

Not sure. He mentioned running Plex in ProxMox which I thought was a VM management environment, although I have no direct experience with it.

johnpoz

@dennypage very true.. proxmox normally are VMs your right. But there are a couple of different ways to run docker.. The container word grabbed my attention.

Proxmox does have support for linux containers - which a lighter form of a full vm, etc..

The bottom line more info would help figure what is going on.

jay_k

I definitely appreciate all the feed back. Honestly I would be lost without it.

I am running ProxMox which will host virtual machines and Linux containers. I have Plex and samba each running in their own container. Pfsense has it's own VM, and I have a VM running docker, which is hosting Radarr, Sonarr, Jacket, Ombi, and Deluge. My NAS is ZFS within ProxMox that is shared using the samba container. The system has 3 NICs. Two that are passed straight through to pfsense (LAN and WAN), and the other is shared, or bridged, for everything else. I am still using my night hawk router in AP mode (that is the 10.0.0.1 IP address, pfsense is on 10.0.0.2). It has both pfsense LAN and the shared NIC plugged into it. The WAN obviously goes to my Starlink modem. Each VM and container has it's own static IP, as well as ProxMox and the nighthawk.

The install is pretty basic. I didn't do any DNS setup that I know of. My interface assignments are:

WAN - igb0
LAN - igb1

I do currently have a line added to the DNS resolver custom option:

server: private-domain: "plex.direct"

I'm not sure what else to post up for my configuration. I left everything else as default.

johnpoz

@jay_k said in I don't think PLEX is connecting to plex.tv:

AP mode (that is the 10.0.0.1 IP address

If its in AP mode why would your client be trying to ask it for dns?

communications error to 10.0.0.1#53: connection refused

You should be asking pfsense for dns 10.0.0.2

dennypage

@johnpoz That pretty much explains it.

jay_k

@johnpoz said in I don't think PLEX is connecting to plex.tv:

If its in AP mode why would your client be trying to ask it for dns?
You should be asking pfsense for dns 10.0.0.2

Well, when you put it that way, It's obvious what's wrong. HA! HA!
I feel like I should have caught that.

I changed the DNS server setting in ProxMox to the correct IP and everything works as it should. It was a setting that was left from the old router. I actually tried to have those two IPs the other way around when installing pfsense, but ran into issues.

I still don't know why this caused playback errors for transcoding, but it all works now.

Thanks so much for all the help.