Jump to content

Emby flooding my network, leading to router crash


zouzougr
 Share

Go to solution Solved by mastrmind11,

Recommended Posts

zouzougr

Hi,

 

I have recently connected Emby to an access point (DD-WRT 192.168.1.2) which is connected to my main Router  (TP-Link 192.168.1.1).

Ever since EmbyServer.exe has been running, I have had constant Router crashes and restarts due probably to some floods whether it's SSDP or UPNP-related or multicasts or whatever the problem seems to be.

Whenever Emby is not running, the network seemed to work flawlessly.

When Emby is on, I have multiple router crashes/reboots and various difficulties in accessing my main router's GUI page beside losing internet connectivity.

With my previous firewall I could not stop specific protocols of Emby from being sourced from my PC and reaching my router and thus causing it to crash,

so I had to stop using emby for my network and internet to work correctly.

Emby's log did not seem to show anything out of the ordinary or erroneous.

 

So I downloaded zonealarm which I am familiar with, I had to put 192.168.1.1 in the list of public zones and adjust Embyserver.exe's access policy to restrict it from accessing internet/public zones.

 

The problem seems to have been resolved so far with emby still servicing other devices on the network while being blocked from addressing the router directly it seems.

 

Kindly advise about this matter and do tell if there is something else which can be done from my side (other than the firewall workaround) or maybe in future releases.

 

Thanks in advance,

 

JG.

 

 

 

Link to comment
Share on other sites

Hi, you could try turning off dlna features and/or the automatic port mapper.

Link to comment
Share on other sites

zouzougr

Hi,

 

I already tried that from Emby DLNA  pane in settings.

Nothing had changed, but now that you mentioned it, if I'm not mistaken, I don't recall rebooting the server (in case it needed rebooting after changing these settings).

I only saved the settings.

Link to comment
Share on other sites

zouzougr

OK this time I saved the settings for disabling DLNA ""and restarted the server"" (disabled also the firewall to see if the problem persists).

the problem remains, now again I cannot access my router and am losing internet connectivity.

Link to comment
Share on other sites

Happy2Play

by "port mapper" do you mean changing the allocated port for Emby ? 8096 ?

Go to Dashboard-Advanced and scroll to the bottom, and you will see the automatic port mapping setting.
Link to comment
Share on other sites

zouzougr

ok , port mapper disabled,  already 5 minutes have passed and everything seems to be running OK so far

Link to comment
Share on other sites

Unless you didn't actually turn the features off, there really is no other explanation. With those features turned off the server will more or less sit there idling.

Link to comment
Share on other sites

zouzougr

what  else other than broadcasting ssdp , multicast for dlna could Emby be addressing the server with ?

The second I set the firewall to block Emby from interacting with the public zones (router IP) everything turns back to normal.

I do understand that the only thing running would be the server at 8096 like a sitting duck awaiting for requests, but something else is happening for sure.

Link to comment
Share on other sites

That's all it's doing it waiting for requests. If you disable dlna play to, dlna server, and automatic port mapping, then there won't be anything outgoing from the server.

Link to comment
Share on other sites

zouzougr

what if it's trying to acquire its port through WAN and failing, what if i port-forward 8096 from the router all the way to my pc (or dmz) ?

do you think that could work ?

 

I just tried to access the public address for emby by the way just now, it failed.

Link to comment
Share on other sites

Happy2Play

Only a log will tell what the server is trying to do.

 

Actually you will probably want to enable Debug logging via the log menu and restart your server.

Link to comment
Share on other sites

zouzougr

I had it enabled already, even though DLNA and port mapper were both disabled, check out this portion of the log :

 

 

2018-06-16 03:10:50.233 Debug PortMapper: Found NAT device: uuid:33333333-0000-c0a8-0101-000000000000::urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:10:50.241 Debug PortMapper: Found device at: http://192.168.1.1/DeviceDescription.xml
2018-06-16 03:10:50.246 Debug HttpClient: GET http://192.168.1.1:80/DeviceDescription.xml
2018-06-16 03:10:50.266 Debug PortMapper: Found NAT device: uuid:33333333-0000-c0a8-0101-000000000000::urn:dslforum-org:service:WANPPPConnection:1
2018-06-16 03:10:50.266 Debug PortMapper: Found device at: http://192.168.1.1/DeviceDescription.xml
2018-06-16 03:10:50.266 Debug HttpClient: GET http://192.168.1.1:80/DeviceDescription.xml
2018-06-16 03:10:50.667 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:10:50.677 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:10:50.681 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:Layer3Forwarding:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceConfig:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceInfo:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:ManagementServer:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:Time:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLInterfaceConfig:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLConnectionManagement:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANDSLLinkConfig:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:10:50.691 Debug PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
2018-06-16 03:10:50.698 Debug PortMapper: Creating port map on local port 8096 to public port 8096 with device 192.168.1.222
2018-06-16 03:10:50.708 Debug HttpClient: POST http://192.168.1.1:80/UD/?9
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:Layer3Forwarding:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceConfig:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceInfo:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:ManagementServer:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:Time:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLInterfaceConfig:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLConnectionManagement:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANDSLLinkConfig:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:10:50.724 Debug PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
2018-06-16 03:10:51.469 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Link to comment
Share on other sites

Happy2Play

With all the port mapper messages I would toggle the setting on, hit save, toggle it off hit save and restart the server and see if the problem still exists.

Link to comment
Share on other sites

zouzougr

is it trying to parse services on the router's port 80 ?

maybe these queries are keeping the router's gui (on port 80) from opening and thus causing some crash in the router ?

Link to comment
Share on other sites

Happy2Play

is it trying to parse services on the router's port 80 ?

maybe these queries are keeping the router's gui (on port 80) from opening and thus causing some crash in the router ?

 

You probably should restart your router when you restart your Emby server/manchine to ensure all the ports are released.

Link to comment
Share on other sites

zouzougr

just did, and still :

 

 

2018-06-16 03:20:50.239 Debug PortMapper: Found NAT device: uuid:33333333-0000-c0a8-0101-000000000000::urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:20:50.239 Debug PortMapper: Found device at: http://192.168.1.1/DeviceDescription.xml
2018-06-16 03:20:50.239 Debug HttpClient: GET http://192.168.1.1:80/DeviceDescription.xml
2018-06-16 03:20:50.253 Debug PortMapper: Found NAT device: uuid:33333333-0000-c0a8-0101-000000000000::urn:dslforum-org:service:WANPPPConnection:1
2018-06-16 03:20:50.253 Debug PortMapper: Found device at: http://192.168.1.1/DeviceDescription.xml
2018-06-16 03:20:50.253 Debug HttpClient: GET http://192.168.1.1:80/DeviceDescription.xml
2018-06-16 03:20:50.654 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:20:50.664 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:20:50.665 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:Layer3Forwarding:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceConfig:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceInfo:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:ManagementServer:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:Time:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLInterfaceConfig:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLConnectionManagement:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANDSLLinkConfig:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:20:50.674 Debug PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
2018-06-16 03:20:50.675 Debug PortMapper: Creating port map on local port 8096 to public port 8096 with device 192.168.1.222
2018-06-16 03:20:50.675 Debug HttpClient: POST http://192.168.1.1:80/UD/?9
2018-06-16 03:20:50.675 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:Layer3Forwarding:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceConfig:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceInfo:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:ManagementServer:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:Time:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLInterfaceConfig:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLConnectionManagement:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANDSLLinkConfig:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:20:50.694 Debug PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
2018-06-16 03:20:51.921 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Link to comment
Share on other sites

  • Solution
mastrmind11

disable the feature, shut down the server, leave it off, power cycle your router(s), let them sit, power up emby server.  there is literally nothing this can be other than DLNA.

  • Like 1
Link to comment
Share on other sites

Happy2Play

If you don't use UPNP you could just disable it on your router also.

PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
Link to comment
Share on other sites

zouzougr

still coming :

 

2018-06-16 03:33:53.511 Debug PortMapper: Found NAT device: uuid:33333333-0000-c0a8-0101-000000000000::urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:33:53.511 Debug PortMapper: Found device at: http://192.168.1.1/DeviceDescription.xml
2018-06-16 03:33:53.511 Debug HttpClient: GET http://192.168.1.1:80/DeviceDescription.xml
2018-06-16 03:33:53.526 Debug PortMapper: Found NAT device: uuid:33333333-0000-c0a8-0101-000000000000::urn:dslforum-org:service:WANPPPConnection:1
2018-06-16 03:33:53.526 Debug PortMapper: Found device at: http://192.168.1.1/DeviceDescription.xml
2018-06-16 03:33:53.526 Debug HttpClient: GET http://192.168.1.1:80/DeviceDescription.xml
2018-06-16 03:33:53.936 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:33:53.941 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:Layer3Forwarding:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceConfig:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceInfo:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:ManagementServer:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:Time:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLInterfaceConfig:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLConnectionManagement:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANDSLLinkConfig:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:33:53.946 Debug PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
2018-06-16 03:33:53.946 Debug PortMapper: Creating port map on local port 8096 to public port 8096 with device 192.168.1.222
2018-06-16 03:33:53.946 Debug HttpClient: POST http://192.168.1.1:80/UD/?9
2018-06-16 03:33:53.951 Debug PortMapper: 192.168.1.1:80: Couldn't parse services list
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:Layer3Forwarding:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceConfig:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:DeviceInfo:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:ManagementServer:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:Time:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLInterfaceConfig:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:dslforum-org:service:WANDSLConnectionManagement:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANDSLLinkConfig:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found service: urn:schemas-upnp-org:service:WANIPConnection:1
2018-06-16 03:33:53.974 Debug PortMapper: 192.168.1.1:80: Found upnp service at: /UD/?9
2018-06-16 03:35:54.132 Info HttpServer: HTTP GET http://localhost:8096/emby/System/Logs/Log?name=embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Link to comment
Share on other sites

zouzougr

Hi, I removed UPNP from both router and access point, disabled it alongside port mapper from Emby, then rebooted all of them.

it's been running well since around 15 minutes so far.

 

It seems to have fixed the problem.

Many thanks, but is there an easier fix so that i could at least use UPNP in my network and most importantly with Emby.

 

Regards,

 

JG

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...