[SUGGESTION] Black/white/ban list for IPs (security issue)

 I will try to use a reverse proxy to solve this.

Unfortunately that may not work well.   I've had limited success trying the same.

There are at least a couple of posts from users who managed to get Reverse Proxy to work after issues following from the recent change from Plex/Web 1.x to 2.x App

Hopefully you would find them when doing google search

site:forums.plex.tv "Reverse Proxy"

There are at least a couple of posts from users who managed to get Reverse Proxy to work after issues following from the recent change from Plex/Web 1.x to 2.x App

Hopefully you would find them when doing google search

site:forums.plex.tv "Reverse Proxy"

Everything I've found doesn't use SSL.  Do you have a link to a post from someone that indeed got a reverse proxy working that uses SSL?

Everything I've found doesn't use SSL.  Do you have a link to a post from someone that indeed got a reverse proxy working that uses SSL?

Can;t remember - but does this help: https://forums.plex.tv/topic/38746-pms-behind-apache-proxy/?p=658472

So you think if a feature doesn't exist, you will make a handmade fix ?

That is part of the open source philosophy.

In this specific case: there is something fundamentally wrong with manually looking through connection logs or any kind of logs for that matter. Normal procedure of any sysadmin is hardening a system, including setting up firewalls, logging and monitoring. People tend to overlook things, or get drunk and forget. Or go on holiday and don't look at the serverlogs for weeks.

Systems should be automatically monitored and escalate. That's why my server has a script that regularly checks that backups have started, processes are running normally, CPU-load is within normal parameters, firewalls didn't see anything suspicious, logins were within normal parameters, etc.. This is a system-wide check, and Plex is just one of the many checks performed.

Plex is not free. If they propose multiuser to Plex Pass accounts, they need to provide a way to manage it, with obvious basic features.

AFAIK, sharing servers is part of the free proposition as well.

There is a basic level of management there: on a user level you can decide if you trust people or not. IP-binding users isn't a way to guarantee security, especially if normally people are using it on mobile phones and tablets with highly dynamic IP-addresses. Using IP-addresses as a quasi authentication token is useless since they change constantly and don't guarantee a thing.

In all honesty I don't see it as a basic feature. Far from it: there are dedicated devices/applications that are specifically designed to filter ip-traffic from the internet to a specific service. It is called a firewall. It can relate IP-addresses to MAC-addresses. It is designed to recognize spoofed IP-addresses. It is designed to handle large volumes of traffic efficiently. A basic principle in software design is not doing somebody else's job, and this typically is the job of a firewall.

There are much more basic functions (like age restrictions) that aren't implemented yet, not to speak of some serious SSL-problems that are still open after months...

Jaap

Unfortunately, no.  But thanks for the effort!