The good news is that there is a modern approach to securely sharing web apps that is worth your attention. In this article, I discuss that while self-hosting your Plex media server is easy, the traditional techniques for providing remote access to it are not. Once the Plex media server is running in the home, many people then want to take the next step and share their content with remote friends and family or enable access to their content while they are away from home on a vacation or business trip. Doing so enables you to own and control your content without the need to upload to a cloud (or pay for it). The server is free to download, self-hosting is easy, and many people run it in their homes. Now if anyone thinks i’ve made a grave error, or there are better/more secure ways to achieve the same, then please let me know in the comments.The Plex Media Server is awesome because it makes it easy to access all your music, photos or videos, and stream to any device. When I enabled remote access again, the status went green and plex was now available outside of the LAN and it immediately fixed my dropouts (missing server, lagging etc) within the LAN. I disabled remote access, specified the public port manually and hit apply. Once this was added, I went into the PMS configuration options and went to the entry remote access: I was told without this rule, i would end up with a relay connection and the bandwidth would be extremely limited. Am sure there are many experts out there that can rephrase this more accurately, but I added it anyway. This is a feature of DNS rebinding in pfSense. Now this last part where you add the custom option to the resolver was necessary because without this, Plex has to use a remote connection even if everything is within the LAN. Plex Wan rules Nat plexpass forwarding rule WAN to LAN Nat plexpass forwarding rule – LAN to WAN Plex DNS Resolver Setting I always find this is helpful for those not that familiar with pfSense. I needed to add a specific entry in the DNS resolver.Anything from MY.: 32400 to go out to the WAN. Then I needed to add a rule to pass the other way.The rule says literally anything coming in on the WAN address pushes forward to MY. Firstly I needed to port forward anything coming in on port 32400 to my internal machine where PMS is running. In order to get past the block that I think my ISP was placing.Even it it’s just an internal IP address (i.e. Please note i’ve redacted various IP addresses and other settings from the pictures for security reasons. It appears that my pfsense install (2.4.4-RELEASE-p3 (amd64)) needed further configuring to allow it to go through. I did some research and eventually came up with a solution. Even internally on the LAN I was having dropouts etc! All work perfectly well with plexpass, so it was frustrating that I couldn’t access this PMS from outside my own LAN. I connect to several servers around the world, one is in my home country, others are back ups that I have abroad. Everything was working perfectly, except the windows based PMS (plex media server) was unable to access the internet properly. I was initially using plexinc/pms-docker on the server (Ubuntu 19.10), but i was suffering from some various shortages and am in the midst of rebuilding a new server, so I opted to run the applet on my main windows machine for now. I am running plex media server on my windows 10 machine and that’s pointed at a share that’s on my server. I travel a lot for work and it’s so convenient for me to just watch films, TV shows and even live TV on my ipad or phone when I’m out and about. So I’m an avid user of plex and am a plexpass subscriber.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |