Its filling up my firewall with hundreds of requests a minute - whats going on?
Details please.
This is coming from plex client on ios
source dest
port port
23:59:59 59911 136.56.xxx.xxx 18045 [2650] <<--- another plex server
23:59:59 59910 82.94.168.40 8443 [2403] <<-- XS4ALL Internet B.V.
23:59:59 59909 192.168.1.194 32400 [5514] <<-- this address doesnt exist
23:59:59 59908 136.56.xxx.xxx 18045 [2650]
23:59:59 59899 192.168.0.11 32400 [5514] <<-- nor does this
23:59:59 59895 82.12.xxx.xxx 13152 [2580]
23:59:59 59894 192.168.0.11 32400 [5514]
23:59:59 59893 82.94.168.40 8443 [2403]
23:59:59 59892 82.12.xxx.xxx 13152 [2580] <<-- a client address
23:59:59 59891 136.56.xxx.xxx 18045 [2650]
23:59:59 59890 82.94.168.40 8443 [2403]
23:59:59 59889 192.168.1.194 32400 [5514]
23:59:59 59888 136.56.xxx.xxx 18045 [2650]
23:59:59 59887 192.168.1.194 32400 [5514]Update - I was able to remove the attempts to connect to 192.168.0.11 by removing a share from one of my friends libraries.
I found this by doing debug logging on the plextv version of the web client.
I cannot however trace where the reference to a server at 192.168.1.194 is coming from. This is not a a valid internal subnet
I have to assume it is from my account on plex.direct but cannot find it (and why only on the IOS client?).
I need to remove this
This also still leaves where the 13152 and 18045 port connection to other friends is coming from. I am able to connect and view those servers with no problem.
And the constant attempts to connect on 8443 to what I think is a plex.direct server
Sorry, but that doesn’t help identify the problem. Please provide the log from the app.
I cannot however trace where the reference to a server at 192.168.1.194 is coming from. This is not a a valid internal subnet
192.168.1.194 would be a local network address. If you have server’s shared with you, the app will check if they are local to you as well. That could be the local address for that shared server.
This also still leaves where the 13152 and 18045 port connection to other friends is coming from. I am able to connect and view those servers with no problem.
This could be your friend’s PMS. PMS can use any external port depending on how it’s configured. Internally (your PMS on the same network) it will always be 32400.
Thank you,
try to get logs for you made me find out how to get them on IOS (which isn’t exactly obvious).
Looking through them (there was a lot) showed that you were correct.
18045 was the external port on a friends remote server and the 192.168.1 address was his local one.
Allowing that port from the network that I was on removed all the entries.
I don’t use that server from the network that I was on so the new client must have changed to try and connect to it regardless.
The other change is the fact that it tries to connect to its local ip, and that it just keeps on trying (over 10,000 times in a couple of hours). This is most definitely a change and a bug. This makes me think that any time a remote server is unavailable my system will be flooded with the client trying different (and illogical) paths to try and reconnect.
There MUST be a cooldown built into this such that it only tries so many times and then sporadically!
@borochris said:
The other change is the fact that it tries to connect to its local ip, and that it just keeps on trying (over 10,000 times in a couple of hours). This is most definitely a change and a bug. This makes me think that any time a remote server is unavailable my system will be flooded with the client trying different (and illogical) paths to try and reconnect.
That doesn’t sound right. It should do 1 check and not check again until the next time, which I believe is 10 minutes. If you can provide the app log showing these attempts, we will take a look.
log attached (full one failed to attach so cut it down to first 200ish lines
Ok. I see the app trying to make connections to those servers. A few every second, so 100s per minute is possible. What I see is that those other servers are shown as being available and online, but when the app connects to those servers, it gets back no info, so it tries again. I’ll have to check how often these retries should happen.
