11/1/2022 0 Comments Plex remote access not working![]()
Any of these options will easily handle a direct play upload speed at original quality. #Plex remote access not working pro#Comcast also has Gibabit Blast Pro service which is a 2Gbps symetric fiber connection. #Plex remote access not working upgrade#My only solution, besides spending a rediculous amount of money on higher end GPUs, is upgrade my internet connection to a provide that will give me 1Gbps symetric speeds (matching upload and download speeds) like Ziply fiber. #Plex remote access not working drivers#I even patched the drivers to unrestrict the number of concurrent streams the card can support for encoding/decoding and set a ram drive with 200GB of ram storage for temp transcode location. It does seem that I can do it if the source media is 264 codec at that high of a bitrate, but if it's 265 codec, my video card struggles to maintain a 1-to-1 play speed vs transcode speed. I was hoping to rely on transcoding on the fly from a 90Mpbs 4k down to 20Mbps 4k for both 265 and 264 codec. So I can't really stream any movies in original quality if their bit rate is higher than 45Mbps. However, comcast limits their 1.2Gbps lines to peak for me is about 45Mbps upload. Also have comcast model in bridge mode so using just my own equipment. I know that my speed with Compcast can hit 1.2Gbps easily from my server (10BaseT NIC to 10BaseT Dedicate Lan router to 10BaseT WAN connection to Comcast 2.5Gps LAN. The titles he is having troubles with are 65Mbps+ 4k titles. However, when I share with my brother in another city, who also has 1.2Gbps internet speed, same as me, he gets throttled trying to do original quality. I also have several nvidia shield boxes in the house doing direct play 4k with over 40Mbps. It's an older 4th gen dual xeon server with 32 cores and an Geforce 1080 graphic card power transcoding. I have 1.2Gbps internet connection where the server is hosted. etc.Click to expand.I have a similar problem as you do, but I do know what my problem is. Maybe his plex is on a new local IP, and he is forwarding to the wrong IP? etc. Finding the missing piece is not possible without some actual info. There are lots of pieces to the puzzle for sure. #Plex remote access not working update#Maybe during the update his public IP changed, or maybe plex is reporting the wrong public IP, etc. I have a specific list in pfblocker that updates those for example. Maybe he is using pfblocker and getting new rules for geoip blocking the IPs that plex uses to check. But that would effect all port forwards, etc. There is a know issue if you have multiple wans, which I do not. So something sure is going on with the OP setup, but what that is impossible to figure out without some basic validation of what is going on. What could possible have changed in an update that every other port forward works, other than plex? And if there was - why is mine working? I would think if there was something the boards would be a flame with users complaining. I've also run looking for port 32400 on my WAN address and it reports: "Problem! I could not see your service on (my public IP address) on port (32400). 09:31:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 53. 09:32:42 WARNING Tautulli Monitor :: Plex remote access port not mapped, ping attempt 54. 09:33:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 55. 09:34:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 56. ![]() 09:35:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 57. 09:36:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 58. 09:37:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 59. 09:38:42 INFO Tautulli Monitor :: Plex remote access is back up. 09:39:42 WARNING Tautulli Monitor :: Plex remote access port mapped, but mapping failed, ping attempt 1. Tautulli has started complaining that Plex is on line and then it's off line. Your server is signed in to Plex, but is not reachable from outside your network." As mentioned, this has worked for years, I do have port forwarding setup (32400 -> Plex server IP). Plex is reporting "Not available outside your network I've recently updated pfSense to 2.5.1 and a couple things have happened. I've been running Plex for quite some time on a FreeNAS box with no problems. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |