Here are my log files. It could be possibly a Double Nat problem. Not really sure how to fix. Still reading and trying to understand the troubleshooting articles. This is not my area of expertise.
I am seeing this error : ERROR - Error parsing allowedNetworks
@keithcq71 said:
I am seeing this error : ERROR - Error parsing allowedNetworks
That sounds like a mistyped entry in the allowed networks option - https://support.plex.tv/hc/en-us/articles/200890058-Require-authentication-for-local-network-access

A double-NAT situation is most easily solved by calling the ISP and asking them for help (setting the modem/router in a bridge mode and/or give you a public IP).
@firefox99 said:
Here are my log files. It could be possibly a Double Nat problem. Not really sure how to fix. Still reading and trying to understand the troubleshooting articles. This is not my area of expertise.
You appear to have disabled Debug Logging. It is on by default but appears to be disabled
And yes you do have Double NAT
Nov 09, 2016 19:01:07.024 [10768] WARN - PublicAddressManager: WAN IP is a private IP address
Nov 09, 2016 19:01:10.532 [10672] ERROR - MyPlex: mapping failed due to potential double NAT configuration
what you need to do is make sure one of the modem/router devices is configured in Bridge Mode.
@keithcq71 said:
I am seeing this error : ERROR - Error parsing allowedNetworks
Nov 10, 2016 04:30:51.522 [6636] ERROR - Error parsing allowedNetworks '136.57.6.12 : 32400 ': An invalid argument was supplied
Two things wrong here
- Syntax is just a network or IP address and not an IP with a port, e.g
192.168.1.109or192.168.1.1/255.255.255.0 - You are no longer able to whitelist WAN IP Addresses - part of the recent Security changes
So delete the entry '136.57.6.12 : 32400 ' in Network Advanced Settings
And please do enable Debug Logging
https://support.plex.tv/hc/en-us/articles/201643703-Reporting-issues-with-Plex-Media-Server
I turned back on debug and retried to place the server online and resent logs. I did purchased the port forwarding tool recommended. But still no luck
sa2000 edit: Logs removed as tokens logging was enabled
@firefox99 said:
I turned back on debug and retried to place the server online and resent logs. I did purchased the port forwarding tool recommended. But still no luck
I have removed your logs. You should never enable logging of security tokens if you plan to share your logs publicly in the forum
Your problem as stated in my earlier reply is a Double NAT - you have your router with a local IP Address as the internet IP. So it must be connected to another router that is also doing NAT translation
Nov 10, 2016 04:57:38.467 [2120] DEBUG - NAT: UPnP, public address is 192.168.50.2
Nov 10, 2016 04:57:38.467 [2120] DEBUG - PublicAddressManager: got WAN IP 192.168.50.2 from router
Nov 10, 2016 04:57:38.467 [2120] WARN - PublicAddressManager: WAN IP is a private IP address
So your first router needs to be changed to be in bridge mode / just a modem and no routing. Talk to your ISP who supplied you that modem/router
Alternatively get rid of your router and just use the ISP supplied modem/router device
Thanks sa2000 . I will try this when I get home
@keithcq71 said:
Thanks sa2000 . I will try this when I get home
you probably have other issues with the setup as that error should just result in the invalid setting being discarded
so enable debug logging
remove the incorrect setting
and restart the server
and reproduce the problem - also double check advice on
https://support.plex.tv/hc/en-us/articles/200931138-Troubleshooting-Remote-Access
I have talked to Google Fiber and Port Foward for that port has been configured correctly . I am confused why I am being told to remove a setting that the Plex software is detecting.
@keithcq71 said:
I have talked to Google Fiber and Port Foward for that port has been configured correctly . I am confused why I am being told to remove a setting that the Plex software is detecting.
I don’t know if we are talking about the same setting
The one that was wrong was you had in this setting:
Settings / Server / Network / Show Advanced
List of IP addresses and networks that are allowed without auth
This setting has nothing to do with Remote Access and Port Forward
What you have in this field is a public IP and then a space character and then colon and then 32400 and then a space character
Not sure why - but this field is intended for specifying local IP Address for legacy devices that cannot authenticate with plex.tv eg LG TV Medialink and LG TV Smartshare as two examples
See this support page for the syntax
https://support.plex.tv/hc/en-us/articles/200430283-Network
So the public IP, which is actually my Google Fiber Network box configuration page needs to be removed , yes? I did not add this and so my question is why is Plex putting this information in?
Up until these update I had no issues nor did my sister who is on my Plex server in another city. Thanks for your help.
@keithcq71 said:
So the public IP, which is actually my Google Fiber Network box configuration page needs to be removed , yes? I did not add this and so my question is why is Plex putting this information in?
Plex would not put it in the field - a person must have done that
Take a screenshot of the server network settings page with show advanced selected and attach here
This is separate matter and the fact that it should not be there should not matter as it is being ignored /
The isssue with remote access could be something else and needs to be investigated with debug logs after restarting the server - but first wanted that setting cleared As it is wrong and filling up logs with errors
Interesting . That I.P. address takes me to my Google Fiber network box. I will remove it but I am now curious how it got added . No one ever has access my PC . This is very strange . Thanks for you help and patience.
I removed that address. That solved the issue. Thanks for the help
@keithcq71 said:
I removed that address.
So now can investigate why Remote Access is not working
Checking what security software you have in place
If there is a firewall rule on the PC as follows
Inbound Port Rule
Protocol : TCP
Local port: 32400
Remote port: any
Remote IP Address: any
Programs : Any
Scope: all profiles
Action: Any
and the usual problem areas outlined on this support page :
https://support.plex.tv/hc/en-us/articles/200931138-Troubleshooting-Remote-Access
Make sure Debug logging is enabled
See https://support.plex.tv/hc/en-us/articles/201643703-Reporting-issues-with-Plex-Media-Server
Check that the local IP Address of the server PC has not changed - you should set it up as a DHCP Reservation or static outside DHCP Range
Ensure Port forward in the router is going to the right local IP Address:
Protocol: TCP
Wan Port: 32400
Local Port: 32400
Destination: Local IP Address of the server PC
Restart the server and try to disable / enable remote access and then with Manually Specify Port ticked and 32400 entered in the box, click the Retry button
If it does not succeed to enable remote access, note down the time and collect the Plex Media Server logs and attach
See
https://support.plex.tv/hc/en-us/articles/200250417-Plex-Media-Server-Log-Files
Lets just look at the logs initially
It appears the new pc I am on a work has blocked me from accessing Plex . Some folks on older PCs can , which is very weird
@Wh4tthehell said:
Ive noted today, that its still sporadic in the on and off with the remote Access.
Sorry took a long time looking at your logs.
Your last logs show some router / uPnP issue where the periodic check Plex Media Server does failed at 08:51
It worked before at each of 05:51, 06:51 and 07:51
This shows a successful sequence
Nov 07, 2016 07:51:19.412 [9304] DEBUG - NAT: PMP, attempting mapping.
Nov 07, 2016 07:51:19.628 [9304] DEBUG - NAT: PMP, mapped port 22592 to 192.168.0.13:32400
Nov 07, 2016 07:51:19.813 [15220] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Nov 07, 2016 07:51:19.866 [15220] DEBUG - NAT: PMP::getPublicIP, Received public IP from router: 50.64.xxx.xxx
Nov 07, 2016 07:51:19.881 [9304] DEBUG - PublicAddressManager: Mapping succeeded for 192.168.0.13:22592.
Nov 07, 2016 07:51:19.897 [15220] DEBUG - MyPlex: Last published value didn't change, we're done.
Nov 07, 2016 07:51:19.897 [9304] DEBUG - MyPlex: Last published value didn't change, we're done.
and this shows a failure when the server was trying to re-establish the uPnP mapping
Nov 07, 2016 08:51:19.409 [20064] DEBUG - NAT: PMP, attempting mapping.
Nov 07, 2016 08:51:19.677 [20064] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Nov 07, 2016 08:51:19.677 [20064] DEBUG - NAT: UPnP, attempting port mapping.
Nov 07, 2016 08:51:19.777 [18408] DEBUG - NAT: UPnP, getPublicIP didn't find usable IGD.
Nov 07, 2016 08:51:20.040 [18408] WARN - NAT: PMP, got an error: NATPMP_ERR_RECVFROM.
Nov 07, 2016 08:51:20.040 [18408] DEBUG - MyPlex: Last published value didn't change, we're done.
Nov 07, 2016 08:51:31.691 [20064] DEBUG - NAT: UPnP, didn't find usable IGD.
Nov 07, 2016 08:51:31.691 [20064] DEBUG - PublicAddressManager: Mapping failed.
I would recommend you switch to having a tcp port forward setup in the router and then select the Manually Specify Port in Remote Access Advanced Server settings and enter the public port you have selected. Many times we have seen reliability issues when using uPnP ports
So suggested course of action,
- Ensure local TCP IP Address for the server 192.168.0.13 is fixed and would not change. Do it as a DHCP Reservation in the router or have it as static IP Address and with it being outside the DHCP Range
- Decide what public tcp port you are going to use - it does not have to be 32400 if you router allows you to have a different port for public/wan from that for local/private in a port forward. Lets for argument sake, say you go for public tcp port 32420
- Setup a TCP Port Forward in the router to port forward WAN/Public Port 32420 to private/local port 32400 and have the port forward assigned to 192.168.0.13
- Save changes
- On the Plex Media Server Settings for Remote Access, select Show Advanced and tick
Manually Specify Portand enter public port32420in the box and click Retry
