Description of problem: Today 2023/09/06 I upgraded to Mageia 9, & noticed that VLC remote control no longer works Version-Release number of selected component (if applicable): - Mageia 9 - VLC 3.0.18 How reproducible: every time I try to connect to PC's VLC using Android's VLC Remote Control Steps to Reproduce: 1. Upgrade to Mageia 9 & install VLC (3.0.18) + lua plugin 2. Open VLC -> Tools -> Preferences -> Show Settings [All] -> Main Interfaces - Extra interface modules - check [Web] - write "http" into the textbox - Lua -> Lua HTTP - enter password -> Save then relaunch VLC 3. Set Firewall to allow Internet connection to tcp/8080 4. Using Android phone I found that VLC:8080 port on PC is opened, (VLC does open the port 8080) but the VLC Remote Control apps failed to connect somehow. I used them to connect to PC (Mageia 8) without any problems.
I can connect using Web browser to http://192.168.x.x:8080 (with limited features) but failed using Android apps.
Thank you for the report, and apologies for the inconvenience it is causing. Unknown territory for me, so let us see that I understand this correctly: You configured VLC for remote control (and the Firewall to allow it); which seems to have been taken into account in that the relevant port 8080 is opened by VLC. You make (or try to) the connection from an Android phone VLC Remote Control application: nothing. Since VLC has changed, it is suspect. Can you say any more about the failure? No messages at all from the phone application? > I used them to connect to PC (Mageia 8) without any problems matters. CC'ing Dave Hodgins who is conversant with ports etc, and will be able to suggest some terminal commands to check the state/usage of the port.
CC: (none) => davidwhodgins, lewyssmith
Quickest way to test/workaround a firewall issue is to add lines to /etc/shorewall/rules.drakx with ... ACCEPT net:10.0.0.0/8 fw ACCEPT net:169.254.0.0/16 fw ACCEPT net:172.16.0.0/12 fw ACCEPT net:192.168.0.0/16 fw ACCEPT net fw icmp 3 - ACCEPT net fw icmp 5 - ACCEPT net fw icmp 8 - ACCEPT net fw icmp 9 - ACCEPT net fw icmp 10 - ACCEPT net fw icmp 11 - ACCEPT net fw icmp 12 - ACCEPT net fw icmp 13 - ACCEPT net fw icmp 14 - ACCEPT net fw icmp 40 - ACCEPT net fw icmp 42 - ACCEPT net fw icmp 43 - Then run (as root) "systemctl restart shorewall.service". That allows all traffic from within your lan. Don't use these rules if you have untrusted guests on the network. Do not run drakfirewall after that. It will not recognize the above lines and will remove them.
It is not firewall problem. 1 application (jbscript.vlcremote) is able to connect but gives tons of annoying errors, while many other applications just fail to connect. It seems to me VLC changed the protocol.
Someone has reported the same issue in the VLC forum: https://forum.videolan.org/viewtopic.php?f=13&t=162774&p=538460&hilit=remote#p538460
Thank you for that link: identical problem. Unfortunately the reporter says nothing about what his PC system is; and is apparently less clued up than you.. Can you add some more meaningful comment to that VLC bug, cross-referencing this one. Ppke that VLC bug; they seem to want to wash their hands of the problem. Even if it is not them, they should be able to suggest how to verify that nad what they think the problem might be. Normally one could ask that you try an earlier version of VLC, but I doubt that this is currently possible with newly released Mageia 9. Assigning this to the packagers for ideas & suggestions. CC'ing two who have committed VLC recently.
CC: lewyssmith => geiger.david68210, ghibomgxKeywords: (none) => UPSTREAMAssignee: bugsquad => pkg-bugs
I can show some errors from jbscript.vlcremote but it is meaningful only to the application developers (Jonny Buchanan et. al.). Meanwhile, normally there is no error message from VLC. According to the Changelog https://code.videolan.org/videolan/vlc/-/raw/3.0.x/NEWS VLC has changed (improved?) the way it handles HTTP connection. I don't know if this caused the bug.
Updated to VLC 3.0.20 but the problem still persists.
mga9 have vlc 3.0.21 in testing repos.
CC: (none) => fri
Why do we still have vlc 3.0.21 lingering in testing repos and I can not find a corresponding bug?
(In reply to Morgan Leijström from comment #10) > Why do we still have vlc 3.0.21 lingering in testing repos and I can not > find a corresponding bug? Don't know Giuseppe send that version
Keywords: (none) => feedback
Giuseppe in private mail now: " For vlc 3.0.21 I added that before the summer, and still actual (so there aren't newer versions, see https://github.com/videolan/vlc/tags), but hadn't time to open the corresponding bug #, basically it improves the stability, and should fix some of the various pending problems of vlc 3.0.18, though I've not checked it fixes all the bugs, and which exactly. "
As 3.0.21 is still latest and already built, I think we should open an own bug for it to get it out. It may not fix the problem described in this bug, but fixes others.
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=33638