#Serviio forum manual
#Serviio forum upgrade

10:45:33,217 WARN Cannot connect to the server to get DB initialization info 10:45:23,084 DEBUG Checking if server is running 10:45:23,084 INFO Connecting to Serviio REST on localhost:23423 10:45:23,056 DEBUG Choosing java look and feel:. 10:45:23,027 INFO Starting Serviio Console 10:45:23,025 DEBUG Listening for application instances on socket 44332 10:45:23,014 INFO Initializing Serviio Console My issue was pretty obvious but wanted to post my experience with this error. This allowed me to keep all of my original settings. I then re-installed Serviio 1.3.1 (did not uninstall first) and was able to launch Serviio and connect to the server from my devices after the reboot. I then restarted Serviio services and launched ServiioConsole.exe, and I still received the same error. I removed the changes made and saved the Profiles.xml. Starting/Restarting the Serviio Service had no effect resulting in the same error.

Seems to be a general connection error thrown when Serviio engages with Java and cannot connect to the server. 11:30:39,205 WARN Cannot connect to server: Connection Error (1000) - Connection refused: connect Message: : Profiles XML file is not valid (according to the schema). 11:30:17,432 ERROR An unexpected error occured.

#Serviio forum manual

Serviio 192.168.10.9 random port sends notify to 239.255.255.250 1900 UDP port, but also 192.168.13.255 1900 UDP port (vlan4) (looking from different vlan than serviio)īut, really I don't understand why, the serviio 'icon' is not available in any devices of different vlans, because the NOTIFY process is present in other vlans.I'm running Serviio 1.3.1, and had this same error after making some manual changes to Profiles.xml Serviio (192.168.10.9) send the notify from random port to 239.255.255.250 1900 UPD port (looking inside same vlan of serviio) I use these configs and scripts and wireshark to trace packets inside my network, I can see that serviio sends from random port to 1900 port the notify, even between diferent vlans. I understand that upnp can't have multi-cast process for different vlans, In my case other users, with my current router config and scripts, can have broadcast in other vlans but using chromecast only. Hope can you help me with these questions. Is there any way to change the ports configurations of serviio to, for example, use UDP 8895 port instead TCP port ? Is necessary broadcast using TCP 8895 port to have serviio working in client devices ? (all devices in same subnet) If I use in practice only UDP 1900 port, can serviio will be avaliable in my smart-tv ? (all devices in same subnet) My question is regarding the ports used in serviio, like wiki says are: UPD 1900, TCP 884 for WEB console. In same vlan, for example lan1, all devices can see and use serviio (like always did in my prior network).

I'm using Ubiquiti EdgeRouter Lite and only have igmp-proxy, mdns, and bcast-relay script to broadcast udp packages to other vlans, many users says that other services like chromecast (that uses 1900 udp port) are available for other vlans using these tools in router (igmp-proxy, mdns, bcast-relay), but in my case I can't have any success. Unfortunately this cause that server vlan (lan1) can't broadcast SERVIIO to other vlans (vlan4 for smart-tv).

#Serviio forum upgrade

I actually read, and learn, more of dlna services.Ĭurrently I'm using a NAS4FREE server with SERVIIO in a jail, I upgrade my network configuration and I'm using vlans to improve performance.