No renderer profiles in serviio-console (Centos 6.3)

Hi,

I know other people had this problem before, but none of their solutions work for me. I'm not forum-savvy, so unsure whether I was supposed to ask there or start a new topic, but I decided to start a new one since those ones were quite stale.

My OS is Centos 6.3, and I've installed serviio by using serviio-1.3.1-linux.tar.gz . My problem is that I do not see anything in the 'Renderer Profile' section of the serviio-console. Also, there is no 'Add' button, so I cannot add a profile myself. The logs seem fine, with no errors, and just the following warnings:

  Code:

...
2013-11-18 11:16:04,003 WARN  [LocalAddressResolverStrategy] Haven't found any suitable local IP address, will try again 9 times
2013-11-18 11:16:09,004 WARN  [LocalAddressResolverStrategy] Haven't found any suitable local IP address, will try again 8 times
2013-11-18 11:16:14,045 INFO  [Device] Created UPnP Device with UUID: 7b463fb7-97cc-377b-ac7d-aa41cffa3c75, bound address: 192.168.169.6
2013-11-18 11:16:14,703 INFO  [ProfilesDefinitionParser] Parsing Profiles definition
2013-11-18 11:16:14,830 INFO  [ProfilesDefinitionParser] Added profile 'Generic DLNA profile' (id=1)
2013-11-18 11:16:14,849 INFO  [ProfilesDefinitionParser] Added profile 'Samsung TV (B-series)' (id=2)
...


and then further down in the log:

  Code:

2013-11-18 11:16:15,792 WARN  [FFMPEGWrapper] FFmpeg is not compiled with libass support, rendering subtitles (hardsubs) will not work.


Other than the above, there are no other warnings or errors.

Changing the bound IP address (in the console) fom 'automatically detected' to a static one does not do the trick for me. Also, I can see the profiles.xml file via http://192.168.169.6:23423/rest/refdata/profiles in a local browser (but not from another computer on the same network) . I should also mention that I'm trying to connect from a Samsung F8000, and that I can get content from my iPhone (over the same wireless network I'm trying to set serviio on). Finally, I should say that I have the following rules added to iptables:

  Code:

ACCEPT     udp  --  anywhere             anywhere            udp dpt:ssdp /* Serviio */
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:8895 /* Serviio */
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:23423 /* Serviio */
ACCEPT     tcp  --  anywhere             anywhere            tcp dpt:23424 /* Serviio */


Thanks in advance for any support, and apologies if i've broken any forum rules.

Regards,

Ross

[zip]

Hi, could you post a screenshot of your problem?

Hi zip, thanks for taking the time to reply.

I have actually fixed this myself a while back; the problem was caused by a conflict between the iptables rules that need to be added for Serviio, and one of the default iptables rules that come with CentOS 6.3. [EDIT - I´ve put some more time into providing a more elgant answer here]

Step 8 of the instructions available at http://wiki.serviio.org/doku.php?id=how ... all:centos says:

8

. IP Tables rules

(I added these to my firewall.sh I run every time I update iptables, if you use another firewall just make sure the correct ports are open)

  Code:

iptables -A INPUT -p udp -m udp --dport 1900 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -p tcp --dport 8895 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -p tcp --dport 23423 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -p tcp --dport 23424 -j ACCEPT -m comment --comment "Serviio"


However, most firewalls have some default `catch-all` reject rules for security reasons. These rules are normally last in the chain, such that the rules before them have a chance to match. Using the above commands however will *append* these rules after the catch-all reject rules. In my instance (CentOS 6.3 and CentOS 6.4) the offending rule was the last one in the INPUT chain:

  Code:

REJECT     all  --  anywhere             anywhere            reject-with icmp-host-prohibited


The most elegant solution that I can think of is to remove the reject rule, add the serviio rules, and then finally re-add the reject rule at the very end. This can be done with the following commands:

  Code:

iptables -D INPUT -j REJECT --reject-with icmp-host-prohibited
iptables -A INPUT -p udp -m udp --dport 1900 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -p tcp --dport 8895 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -p tcp --dport 23423 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -p tcp --dport 23424 -j ACCEPT -m comment --comment "Serviio"
iptables -A INPUT -j REJECT --reject-with icmp-host-prohibited


N.B. in your instance, you may have other rules that cause trouble. The best way to identify them is to see what rules match while trying to connect your devices, and you can do this with the following command:

  Code:

watch ´iptables -vL´

The packet counts for the matching rules will be increased as packets pass through iptables.

Hope this helps someone.

All the best,

Ross