Hello, As I was saying yesterday :
------ Okay I was right, that’s the nobody parameter that make the issue, I’ve edited /etc/init.d/red5 and remove –c nobody in the line : start-stop-daemon --start -c nobody --pidfile $PIDFILE \ And that works … Ok so Maxim, it’s a permission port issue, I know now why that was working before switching to SSL ports. Thanks BTW. -------- I think my mail had been blocked or sort of … Clem De : IamTutor Rus [mailto:iamtutor...@gmail.com] Envoyé : mercredi 10 décembre 2014 15:39 À : user Objet : Re: problem with boot script You can try to forward 443 port with iptables and start service on port above 1024. 2014-12-09 18:43 GMT+03:00 Maxim Solodovnik <solomax...@gmail.com>: user in /etc/init.d/red5 script might also need to be corrected to be root On Tue, Dec 9, 2014 at 9:43 PM, Maxim Solodovnik <solomax...@gmail.com> wrote: Hello Clem, Only super user have rights to run services on ports below 1000 please run /etc/init.d/red5 as root or search for workaround in internet (unfortunately I have no solution for this :(( ) On Tue, Dec 9, 2014 at 9:33 PM, Clémence TRAMIER <clemtra...@gmail.com> wrote: Hello, At last, i’ve succeed to make my openmeetings work in HTTPS and RTMPS, that works with red5.sh manually launched. But If I reboot the server, only the rtmps is running, no https, when I go in logs, it tells me : Failed to initialize end point associated with ProtocolHandler ["http-nio-0.0.0.0-443"] java.net.SocketException: Permission denied I think that is “nobody” related, but I don’t know how to resolve this… It’s so frustrating that doesn’t work at boot … Can you help me please. Thanks Clem -- WBR Maxim aka solomax -- WBR Maxim aka solomax
