#Plex remote buddy tv

I limit these standard port 443 to US ips. Same goes for my request system, while this also requires login. With all things related to security it always comes down to level of security vs ease of use. And I want to be able to share with my friends and family - and relay (outbound only is too slow 1 or 2mbps limit if your plex pass - I am), and locking to their ips while that would be next best option to vpn is too much work. I sure and the F am not going to spend the time, effort and most likely my own money to do that. How am I going to get them to setup a vpn to my pfsense.

#Plex remote buddy tv

But then I have family that just has shit isp wifi router, and their tv is connected to the wifi.

Yes if it was just you - by all means vpn in to your network vs exposure - agree 100%. I don't see any in the last 24 hours, 2000 log entries. Part of the reason I put mine on a different port then 32400 on external - was to be able to see how many scans just to 32400. And some of them travel about, my one buddy spends time down in FL for example at different Air BnBs - yeah he is crazy during covid. But this was just to difficult for typical users )Īnd they change, and then they can't access from their phones while on cell data, etc. I limit who can hit my open ports using pfblocker, only US ips - I at one time had the users give me their public IPs. You have to auth through their service, and you can now enable 2fa if you want. Mine starts with 64, but that is my actual pfsense wan IP. Notice the IP plex is showing for its external in the remote setting. Remote clients trying to go to X would never get to your plex. Is plex actually seeing your correct public IP? If you are routing traffic out a vpn for example - plex might think its X, while your real wan is Y.

I allow only US Ips, and the IPs from external check I do with status cake to notify me if plex goes down, and the IP that plex uses to check if plex is available remotely - these IPs sometimes change. I have added to this list the status checking IPs they use to see if your plex is open. I currently use different external port, but it sends to plex on 32400.Īre you using say pfblocker auto rules to block countries? Or Ips - notice I use in my rules pfblocker to limit who can talk to plex.

Do you have rule on top of the rule that allows that could block? Users quite often say they did X, but find out they really did A+B^12x42ĭo have any floating rules? What version of pfsense are you on? Do you have multiple wan? There is a known issues with port forwards and multiple wan only working with default gateway, etc. While running the test from the external - sniff on your wan and validate that traffic gets there. Lets call it security through obscurity ) This is a way I can see what is just scanning or plex, and who are my true clients. I use a different external port than internal - but this doesn't really matter for the sake of discussion. First test is to validate traffic actually gets to your pfsense wan.

Low power nas, with decent enough umph to handle multiple clients on 1080. And yes for last few years this has been on my synology nas (ds918+) Which works great btw. And have many many people using it remotely. I have been running plex behind pfsense for years.