Why can't Plex find my local IP?

Plex Media Server Desktops & Laptops
1

As you can see in that screenshot, Plex can’t find my local IP. I’m having other connection issues, but I’ll deal with those later. What does the error “Unknown IP” mean?

2

I get the same thing on my Samsung TV …

3

@ibigfire said:
https://lh3.googleusercontent.com/-mWT4UiD5yuo/V7lJVMiKgcI/AAAAAAAAMNc/IYPPP3ojcS4/s0/firefox_2016-08-20_23-25-15.png

As you can see in that screenshot, Plex can’t find my local IP. I’m having other connection issues, but I’ll deal with those later. What does the error “Unknown IP” mean?

Could you retry the remote access connection
Are you using a port forward in your router of public port 32400 ?
If you are then you would need to tick manually specify port and have the 32400 in the port field

The unknown IP text has been seen before and there is an investigation at the moment for a suspected timing issue to do with checking reach ability -
You could restart and then wait few minutes and if problem persists and even after disabling and re enabling remote access, then get the Plex Media Server.log uploaded here with screenshots and details of what you have for port forwarding

https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files

4

I retried the remote access by disabling and re-enabling it. Same issue.
I do have port 32400 forwarded in my router, since UPNP is sometimes unreliable. Why would I have to manually specify the port that it uses by default? Either way, since it shouldn’t matter, I did it anyway.

Same issue.

Alright, on to the next. I restarted, waited 10+ minutes just to be sure, and still have the same problem. I’ll upload the log. And here’s a screenshot of my current port forwarding settings. https://lh3.googleusercontent.com/-z1ZLSwb76hI/V7qv6P-i_zI/AAAAAAAAMOk/M1LpMnuZuUQ/s0/firefox_2016-08-22_00-55-16.png

5

@ibigfire said:
I retried the remote access by disabling and re-enabling it. Same issue.
I do have port 32400 forwarded in my router, since UPNP is sometimes unreliable. Why would I have to manually specify the port that it uses by default? Either way, since it shouldn’t matter, I did it anyway.
https://lh3.googleusercontent.com/-rXa4euNn53s/V7qZ_h_uJDI/AAAAAAAAMOM/xxSn8DPJVxg/s0/firefox_2016-08-21_23-21-46.png

Same issue.

Alright, on to the next. I restarted, waited 10+ minutes just to be sure, and still have the same problem. I’ll upload the log. And here’s a screenshot of my current port forwarding settings. https://lh3.googleusercontent.com/-z1ZLSwb76hI/V7qv6P-i_zI/AAAAAAAAMOk/M1LpMnuZuUQ/s0/firefox_2016-08-22_00-55-16.png

Thanks - it is the default port when manually specify port is selected. So leave it ticked as selected and 32400 specified

Can you remove all the other port forwards in your router for Plex leaving only the 32400-32400 one
The others are not meant to be for forwarding - but simply specified on this support page so that you allow them through the firewall. See note at the bottom https://support.plex.tv/hc/en-us/articles/201543147-What-network-ports-do-I-need-to-allow-through-my-firewall-

Also to tidy up a bit and simplify setup, please disable support for ipv6 in server settings / network / show advanced

I am seeing in the log the warning due to out of sequence handling of events - what has been also seen in other logs where we had the Unknown IP reported

Aug 21, 2016 23:44:33.068 [7980] DEBUG - EventSource: Got event [data] '<Message address="70.78.xxx.xxx" port="32400" asyncIdentifier="2cdb4df7-0db3-4695-8fe1-7b1a617ddb96" connectivity="1" command="notifyConnectivity"/>'

Aug 21, 2016 23:44:43.384 [7980] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier

I will flag this to the development team

6

Getting the message “plex PubSub Received notify Connectivity event with incorrect async” everytime I try to enable remote access. It formerly worked fine - but now fails everytime. My router settings (which previously worked great) are still:

Port Forwarding
Service Name Type Start Port End Port Server IPv4 Server IPv6 Active
plex TCP/UDP 32400 32400 172.16.2.4

What is “interesting” is that after clicking “retry” on remote access, I get “green” acceptance - then the incorrect async message and then “red”.

7

Should have posted this with my bug report above…

System Information:
Linux media 4.4.104-39-default #1 SMP Thu Jan 4 08:11:03 UTC 2018 (7db1912) x86_64 x86_64 x86_64 GNU/Linux

Plex Version: Version 1.11.1.4760

8

I’ve found that if I set my PLEX media server to manually use port 32400 and restart the server multiple times, it will sync up and permit remote access.

9

Currently running into this as well after I ported my plex server over to a vm. canyouseeme shows port 32400 as open, jumbo frames are disabled. I can also access the server from outside its network via my global ip. retrying the connection ends with it being fully accessible to not being accessible after a second or to. also seeing the “PubSub: Received notifyConnectivity event with incorrect async identifier” in the logs.

Linux lin-virt06 4.15.6-1-ARCH #1 SMP PREEMPT Sun Feb 25 12:53:23 UTC 2018 x86_64 GNU/Linux
Version 1.12.0.4829

One last detail. I had it working for roughly a day before it disconnected with this error.

Any help would be appreciated.
Thanks

10

@“lyle.bickley” said:
I’ve found that if I set my PLEX media server to manually use port 32400 and restart the server multiple times, it will sync up and permit remote access.

There is a timing issue that results in the async identifier issue where messages are received out of sequence and may give rise to the wrong status indication being set on the remote access sett8ngs page

Avoiding quick and repeated clicks on retry would reduce the chances of getting the problem

11

@Xarin said:
Currently running into this as well after I ported my plex server over to a vm. canyouseeme shows port 32400 as open, jumbo frames are disabled. I can also access the server from outside its network via my global ip. retrying the connection ends with it being fully accessible to not being accessible after a second or to. also seeing the “PubSub: Received notifyConnectivity event with incorrect async identifier” in the logs.

Linux lin-virt06 4.15.6-1-ARCH #1 SMP PREEMPT Sun Feb 25 12:53:23 UTC 2018 x86_64 GNU/Linux
Version 1.12.0.4829

One last detail. I had it working for roughly a day before it disconnected with this error.

Any help would be appreciated.
Thanks

See my post above regarding the timing issue. It should only affec the status indicator And remote access should still work - a browser refresh on the settings for remote access page may correct the indicator - similarly a restart

12

Waking a several month old thread, but, I’m getting hundreds of the async errors a day, for many weeks now. Even posted a new thread that no one seems to be interested in.