upnp not working

[BobbyDing 56]

Hi Folks,

I had my two Emby servers (1 win 7, one unraid) shut down for a couple months while I worked on some other issues with the unraid machine. This past week I restarted Emby (windows 7) and updated it. All is working except the upnp for external access stopped working. I no longer see Emby on the upnp list of port forwarding. I do see the upnp list on the router routinely updating and it picked up a new install of playon, so that appears to be working. I turned off the windows 7 firewall and still no go. It is using the standard Emby ports 8096 and 8920 for internal and external. I do have an external domain and the boxes for https reporting and enable automatic port mapping. I have shut down and restarted Emby, as well as disabled/enabled upnp on the router. Earlier today I also rebooted the router. It is odd as this used to work fine. Plex and playon upnp are still working. I also stopped this server and tried the unraid version with the same results. I'll stick to troubleshooting the windows version for now. Posting the log. Any ideas?

 

Thanks,

 

Bobby

EMBY LOG.txt

Edited March 21, 2017 by BobbyDing

[Luke 42080]

What kind of router do you have? unfortunately this is something that has to be tested with each device individually and unless we happen to have the same model or brand for testing it may be difficult to chase down.

 

Keep in mind, the only thing this is doing is mapping public ports to local ports on your server machine. It would be great to get the automatic mapping working but this is also something that can be set up manually in the router and only takes a couple minutes. 

 

Thanks !

[BobbyDing 56]

Hi Luke. Thanks for the response. The router is an Actiontec MI424WR Rev I. It came with the Verizon service, now Frontier. I know I can set the port forwarding manually. It's just that upnp used to work on this exact same router with Emby a couple months back. I was hoping somebody might have had a similar experience and might be able to suggest just how to jiggle the handle to get it to work again. Questions.....What line(s) in the log show that it's requesting the port mapping? and will Emby do the upnp request each time I untick/tick the "Enable automatic port mapping"?

 

Thanks!!

[dcook 299]

1st thing you should do when setting up home internet is turn off uPNP it is very dangerous to leave uPNP enabled.

 

If you ask anyone, or google search you will see that it should be turned off or disabled.

[Luke 42080]

2017-03-20 21:16:47.8495 Debug PortMapper: NAT device found: 192.168.1.194
2017-03-20 21:16:47.8495 Debug PortMapper: NAT device found: 192.168.1.194
2017-03-20 21:16:47.8495 Debug PortMapper: Found NAT device: uuid:445269bc-ed9f-39d6-a86b-a975069c1d8d::urn:schemas-upnp-org:service:WANPPPConnection:1
2017-03-20 21:16:47.8495 Debug PortMapper: Calling Nat.Handle on uuid:445269bc-ed9f-39d6-a86b-a975069c1d8d::urn:schemas-upnp-org:service:WANPPPConnection:1
2017-03-20 21:16:47.8495 Debug PortMapper: Found device at: http://192.168.1.1:2555/upnp/f541be8e-de74-32a1-8d5b-9a03a85ccd5d/desc.xml
2017-03-20 21:16:47.8495 Debug PortMapper: Parsed device as: 192.168.1.1:2555
2017-03-20 21:16:47.8495 Debug PortMapper: Fetching service list: 192.168.1.1:2555
2017-03-20 21:16:47.8495 Debug PortMapper: NAT device found: 192.168.1.194
2017-03-20 21:16:47.8495 Debug PortMapper: NAT device found: 192.168.1.194
2017-03-20 21:16:47.8495 Debug PortMapper: Found NAT device: uuid:445269bc-ed9f-39d6-a86b-a975069c1d8d::urn:schemas-upnp-org:service:WANPPPConnection:1
2017-03-20 21:16:47.8495 Debug PortMapper: Calling Nat.Handle on uuid:445269bc-ed9f-39d6-a86b-a975069c1d8d::urn:schemas-upnp-org:service:WANPPPConnection:1
2017-03-20 21:16:47.8495 Debug PortMapper: Found device at: http://192.168.1.1:2555/upnp/f541be8e-de74-32a1-8d5b-9a03a85ccd5d/desc.xml
2017-03-20 21:16:47.8495 Debug PortMapper: Parsed device as: 192.168.1.1:2555
2017-03-20 21:16:47.8495 Debug PortMapper: Fetching service list: 192.168.1.1:2555
2017-03-20 21:16:47.8495 Debug PortMapper: NAT device found: 192.168.1.194
2017-03-20 21:16:47.8495 Debug PortMapper: NAT device found: 192.168.1.194
2017-03-20 21:16:47.8495 Info HttpClient: HttpClientManager POST: http://192.168.1.1:2555
2017-03-20 21:16:47.8495 Error HttpClient: Error getting response from http://192.168.1.1:2555

The router is then returning a 500 response code which means it's rejecting the request for whatever reason.

[BobbyDing 56]

I will turn off upnp and forward the ports manually.

 

Thanks!!

[Luke 42080]

Thanks for the update.