Connect refused after a few seconds.

[pr3dict 33]

I restarted my server and I couldnt access the web gui anymore. It says connection refused on chrome. I restarted the emby-server service and I was able to access the gui for a few seconds and then it started giving me connection refused again.

 

Any idea why its doing that? 

 

I can keep restarting the server and access some pages for a few seconds but then it locks me out again.

 

Attached are the logs.

 

 

Emby server log 161106.txt

[Luke 42077]

All outgoing network requests from Emby server are failing for whatever reason. Looks like you have a network problem of some sort going on.

[Luke 42077]

By the way this includes not just requests going out to the internet but local network requests as well. Everything serverwmc is attempting to do on the local network is also failing for instance.

[pr3dict 33]

I have two nics in my server, which one is it trying to use? Also, ServerWMC is not installed on this machine and the machine it is connected to is turned off right now, is that causing the issue?

 

EDIT: also, thanks for the quick response, I appreciate that you are on top of these questions all the time.

Edited November 6, 2016 by pr3dict

[Luke 42077]

Well nonetheless, I can only report what I am seeing and the log you have provided contains network errors coming from the ServerWmc plugin. Perhaps try removing the plugin and rebooting again.

[pr3dict 33]

I just removed it and nothing changed. I restarted the machine also. Is there a way I can reset the network configuration? the machine responds to ping requests so Idk what else is wrong.

[pr3dict 33]

something has to be corrupt... It starts up fine for a few seconds and I'm able to access the server, then it goes and tells me that the connection is refused. That has to be because there is nothing listening on that port on emby or emby just cant answer my computer. The fact that it answers originally means that there is no firewall issue. 

[Luke 42077]

the log also had a failure coming from the realtime monitor in a way that we're not able to catch. that could be causing the crash. if you only have a few seconds then you may need to go through the config files manually under /var/lib/emby-server/root/default and set the library monitor to false.

[pr3dict 33]

well you fixed it... I forgot that when I restarted the server I never remounted the folders that I have remotely. That caused the server to crash I guess as it was looking for media folders that didnt exist.