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

[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.