My Serviio Service does not detect any device

Good morning,

I am an user of Serviio and I have been using for over a year but suddenly it stopped working. I checked everything and it was the same as before except for the accesses to the Serviio service.

I am attaching information so you can help.

I have a Windows 10 Home operative System. The IP of my PC is assigned to 192.168.1.5 and it runs Serviio as service.

The Internet adapter is Realtek PCIe GbE Family Controller, and it is selected as that in the Serviio Console.  

I also have the Serviio running as service in my Windows 10 Home.

Everything seems as before it stops working except for the Serviio Console.

The only connected device is my own PC running the Serviio service.

I tried editing the “user.vmoptions” file, which is empty, but I do not know how to edit it or fix it.

In my router I have opened the port 1900 UDP and 8895 TCP for my PC 192.168.1.5

Finally, in my Kaspersky I can see the two ports opened, the port 1900 UDP is assigned to 192.168.1.5 and it is opened but the port 8895 TCP is assigned to ip 0.0.0.0 and opened. That could be the problem, but I do not really know.

Does anybody run into this before?

Best regards,
Daniel

[atc98092]

I think the issue is your Kaspersky settings blocking access. I can't say for certain what that one setting should be, as I don't run any firewall on my home PCs. I'm not overly concerned about something inside my home network. Every computer has A-V running.

That said, I do see a lot of Java errors in that log, all pointing to a date/time issue. I have no idea where it's coming from, other than it's a Java error. Since your log appears to have an accurate time stamp, and that time comes from the operating system, I wouldn't think your computer date/time is wrong. But you might check your router and ensure it has the correct date/time.

There's no need to open any ports on your router. Those ports are for passing traffic between your home network and the Internet. DLNA cannot be routed over the public network, so there's no need for that. However, that still doesn't mean your router isn't a problem. One thing that worked for another user was to add a network switch that all your internal devices connect to, then run a single Ethernet cable from the switch to the router. That would eliminate anything in the router itself as the issue. Of course, that wouldn't change anything for devices that are using WiFi instead of a cable to connect.

The fact it was working fine, then suddenly stopped working, implies there was a change in one of three places: the network, the Serviio PC, or the device trying to connect to Serviio. This change was most likely software related. From the Serviio log I would say that Serviio itself is working fine, other than the date/time issue. That leaves either your firewall (Kaspersky) or the operating system (Windows). Windows has been known to change its firewall settings after an update. Even though you're running Kaspersky, it's possible the Windows firewall has activated and is blocking access to Serviio. I suggest checking those settings. And as mentioned, the Kaspersky setting might be the culprit as well.

Thank you for your reply act98092.

The kaspersky is not the issue, after reading your answer I stopped kaspersky and tried and still did not work.

The router has the same date/time as the PC, but as you said there was a change in the network. I connected through a switch 5 PCs that before were connecting to the network via PLC. My router may not have enough memory to handle all that. So my question is, should I try fix the Java errors or those could be caused by the router? I may try with another router.

[atc98092]

I'm not familiar with what the Java error means. Java often puts messages in the log that look like errors, but Serviio runs just fine. Hopefully Zip will see this post, as he would be the best to answer that.

I'm not certain what you mean by connecting to the network via PLC. Is that a piece of networking equipment? If your devices are all connected via a simple Ethernet switch, then there should be nothing network wise that would be causing Serviio not to appear. But something beyond a switch might have some sort of routing rules or something similar that is mucking things up.

The PLC I use is the brand Devolo, it means "Power Line Communication" and from one socket it goes through the power line (electricity) to another PLC device plugged in another socket.

[atc98092]

Ah, got ya. Some people have reported issues with uPnP across powerline networking adapters. I don't know if it's common or specific to certain brands. If you could run a temporary Ethernet from the TV to the main network switch, bypass the powerline section, and see if Serviio reappears.