Unfortunately I can't help with CentOS FW :( Maybe in addition to your firewalld there is some other stuff? like iptables? or something?
On Fri, Jan 12, 2018 at 9:57 PM, Андрей Прицепов <p.and...@fort.crimea.com> wrote: > I tried connect from windows machine as client. From Ubuntu as client. Both > server is centos7. > First message that I wrote in this theme is note relevant, it was problem > somewhere in the middle, for good time forget about it. > My problem for now I can't connect from other machine to > https://192.168.0.X:5443/openmeetings, 192.168.0.X is IP of my centos7 server > OM. > When I stop firewalld it is no problem to connect by those link, but if I > start firewalld, it become not accessible, that is my problem for now. I can > connect whatever firewall stop or start only if I connect from centos7(gui) > by link https://localhost:5443/openmeetings. > > Error in browser when firewalld started standard: > Unable to connect > Firefox can’t establish a connection to the server at 192.168.0.X:5443. > The site could be temporarily unavailable or too busy. Try again in a few > moments. > If you are unable to load any pages, check your computer’s network > connection. > If your computer or network is protected by a firewall or proxy, make > sure that Firefox is permitted to access the Web. > ------------------- > С уважением, Андрей Прицепов “Лаборатория Форт Крым” > > > -----Original Message----- > From: Maxim Solodovnik [mailto:solomax...@gmail.com] > Sent: Friday, January 12, 2018 4:54 PM > To: Openmeetings user-list > Subject: Re: firewalld settings on Centos7 > > Are you testing screen-sharing app on CentOS? > According to your screen-shots it is most probably windows machine. > > In this case screensharing.log will be in your home folder at Windows machine > ...... > > Why are thinking your screen-sharing app is blocked by the FW? > > On Fri, Jan 12, 2018 at 7:50 PM, Андрей Прицепов <p.and...@fort.crimea.com> > wrote: >> More >> I look file "cat /opt/red5401/conf/red5.properties|grep port", as I see >> ports list: >> 843 >> 5080 >> 5443 >> 1935 >> 8443 >> 8088 >> 8081 >> 1936 >> 1935 >> 9999 >> 9998 >> >> I add all this ports to exception by "firewall-cmd --add-port=%port from >> list, up%/tcp" , "firewall-cmd --add-port=%port from list, up%/udp" >> Then "systemctl restart firewalld.service" >> Whatever, openmeetings doesn’t work in my local network from other >> machines, only from https://localhost:5443 Maybe something more I need to >> add to exception. Not only ports? Can you give me advice? >> >> >> ------------------- >> С уважением, Андрей Прицепов “Лаборатория Форт Крым” >> >> >> -----Original Message----- >> From: Андрей Прицепов [mailto:p.and...@fort.crimea.com] >> Sent: Friday, January 12, 2018 2:24 PM >> To: user@openmeetings.apache.org >> Subject: RE: firewalld settings on Centos7 >> >> I see my file /home/user/screensharing.log but last what I see I date >> 20180111. I reboot centos7, repeat error, but I don’t see in screensharing >> logs for 20180112. Even more after reboot centos7 I enable firewalld to >> start it automatically, and now I can't access to openmeetings. If I stop >> service firewalld it is works as expected. What rules should I add to >> firewalld? In my case I got https over http, other settings is default. I >> can't see in screensharing errors to repeat it, I don’t understand why in >> this file doesn’t exist yet strings for today. >> >> ------------------- >> С уважением, Андрей Прицепов “Лаборатория Форт Крым” >> >> -----Original Message----- >> From: Maxim Solodovnik [mailto:solomax...@gmail.com] >> Sent: Friday, January 12, 2018 3:32 AM >> To: Openmeetings user-list >> Subject: Re: firewalld settings on Centos7 >> >> Ports you have to open depends on your red5 server configuration >> Please check screensharing.log file (on client machine, in HOME >> folder) and ensure what protocol/port is being used And what is the >> error >> >> On Thu, Jan 11, 2018 at 7:52 PM, Андрей Прицепов <p.and...@fort.crimea.com> >> wrote: >>> I on firewalld.service and add rules: >>> firewall-cmd --add-port=5443/tcp >>> >>> firewall-cmd --add-port=1935/tcp >>> >>> But I got error when I try to “start record”, see screenshot attached. >>> >>> Did I something miss, add more rules? I use https, at last I >>> configure https, but I don’t configure rtmps because I think it is no need >>> to do this. >>> So minimal is done 5443,1935 ports add to exception. >>> >>> >>> >>> ------------------- >>> >>> С уважением, Андрей Прицепов “Лаборатория Форт Крым” >>> >>> >> >> >> >> -- >> WBR >> Maxim aka solomax >> >> > > > > -- > WBR > Maxim aka solomax > -- WBR Maxim aka solomax
