Limit remote stream quality and "Not enough Bandwidth"

General Discussions
41

It happend to me just with trailers, i have 70MB FTH internet, somebody know hot to fix it?

42

@owtlaw333 said:

@sa2000 said:
Just to add to the above - your local subnet appears to be 212.232.3.xx which is a WAN IP Address range
Any reason for not using a Private Network IP range.?

There was reason years and years ago… no reason exists now other than it’s what I’ve used for so long and have never had a need or urge to reconfigure.

@owtlaw333

FYI
It is owned and used publicly as well. If you ever needed to route to these REAL networks (probably unlikely) it owuld fail internally. Alternatively, you would have to make sure all clients had access to this subnet directly, otherwise it would route to Europe to try to find the real IP instead of your internal IP. It may not be worth changing, but there is a real reason not to use it.

Responsible organisation: LLC “Real-net”
Abuse contact info: abuse@real-net.pro

inetnum:         212.232.0.0 - 212.232.7.255
netname:         REAL-NET
descr:           LLC "Real-net"
country:         RU
admin-c:         RN3331-RIPE
tech-c:          RN3331-RIPE
status:          ASSIGNED PA
mnt-by:          MNT-REAL-NET
mnt-lower:       MNT-REAL-NET
mnt-routes:      MNT-REAL-NET
notify:          nk@real-net.pro
created:         2015-02-19T11:59:18Z
last-modified:   2015-02-19T11:59:18Z
source:          RIPE


role:            Real-Net NOC
address:         LLC Real-Net
address:         Prostornaya 1A
address:         Voronezh
address:         Russian Federation
phone:           +79204420334
fax-no:          +79204420334
e-mail:          nk@real-net.pro
admin-c:         NK3059-RIPE
tech-c:          NK3059-RIPE
nic-hdl:         RN3331-RIPE
mnt-by:          MNT-REAL-NET
abuse-mailbox:   abuse@real-net.pro
notify:          nk@real-net.pro
created:         2014-06-20T09:36:34Z
last-modified:   2015-02-27T10:12:16Z
source:          RIPE


route:           212.232.0.0/20
descr:           LLC Real-Net
origin:          AS13178
mnt-by:          MNT-REAL-NET
created:         2010-03-15T09:16:54Z
last-modified:   2015-02-19T11:17:55Z
source:          RIPE
43

@drinehart said:

@owtlaw333 said:

@sa2000 said:
Just to add to the above - your local subnet appears to be 212.232.3.xx which is a WAN IP Address range
Any reason for not using a Private Network IP range.?

There was reason years and years ago… no reason exists now other than it’s what I’ve used for so long and have never had a need or urge to reconfigure.

@owtlaw333

FYI
It is owned and used publicly as well. If you ever needed to route to these REAL networks (probably unlikely) it owuld fail internally. Alternatively, you would have to make sure all clients had access to this subnet directly, otherwise it would route to Europe to try to find the real IP instead of your internal IP. It may not be worth changing, but there is a real reason not to use it.

Good thing I don’t visit too many Russian websites, lol. I think I’ve had this configuration for 12+ years at this point and the only device I’ve had that didn’t play well with it was the Roku (more specifically, the app) which I subsequently returned.

But we’ll see… maybe on my next overhaul I’ll think about reconfiguring everything.

Thanks for the info!

44

@gtosnipey said:
I’m experiencing this also. Happened last week when I was at a hotel, and now today on the PS4 (a friend also reported it to me). I guess the temporary solution for everyone is restarting their plex server once a day?

I restart my server once a day to keep it fresh and going smoothly. Helps a lot.

Just make a scheduled task to run in the early morning after your background maintenance task is done. In windows, run scheduled tasks in control panel, make a new task. Trigger would be the time to do it. For actions, add in the program “shutdown.exe” in the system32 folder. For arguments add in /r … for reboot. There ya go. Now your server will reboot on its own every morning when most likely no one is using it.

45

I’m having these issue with new install of Version 1.9.6.4429 from FreeNAS plugin…
solutions above don’t help

46

@thejrose1984 said:
I’m having these issue with new install of Version 1.9.6.4429 from FreeNAS plugin…
solutions above don’t help

The current version of Plex Media Server is
1.11.0.4633 (Beta for Plex Pass)
1.10.1.4602 (General Release)

Bugs relating to bandwidth limit errors when using plugins such as iptv were fixed recently
Most recent fix was in 1.10.1.4561 Beta release - which is included in the 1.10.1.4602 (General Release)

See release notes http://forums.plex.tv/discussion/62832/plex-media-server#latest