Never saw such errors before Do you have anything in the logs? (both OM logs and server logs) Sounds like even: OM has been restarted from time to time (happens then server is out of free resources CPU and/or RAM) Or your provider drops/reconfigure your inet connection
On 22 July 2014 14:59, Huy Minh Huỳnh <huy.h...@gmail.com> wrote: > Hello guys again, > > I changed the port to 80 but the problem apparently still exists. > It's a bit better now since the outer clients are able to connect to > openmeetings server and join the conference. However, after a short moment > (like 3-5 minutes), the connections are dropped and outer clients cannot > connect back to the server. At that time I also can't telnet to the server > at port 80 from outer client. > But in like 5 minutes, we all can connect to the server again... > I still have no idea about this problem. > > Anymore help is highly appreciated. > On Jul 17, 2014 3:38 PM, "Huy Minh Huỳnh" <huy.h...@gmail.com> wrote: > >> Thank guys. >> >> Apparently, on the outer clients, the port 5080 are closed but not on the >> openmeeting server. >> However, when i used the command iptables -L on clients, it show that the >> clients' firewalls allows all incoming and outgoing connections including >> those from port 5080. >> I'm suspecting that the culprit is our external router's firewall, >> however, I can't contact the guy in charge of network management now. >> I will let you guys know the result later when he's available. >> >> Best regards, >> Huy. >> On Jul 17, 2014 3:18 PM, "Maxim Solodovnik" <solomax...@gmail.com> wrote: >> >>> please try >>> telnet your_outer_ip 5080 >>> >>> in case it will fail you need to configure your network >>> >>> >>> On 17 July 2014 14:50, Vasiliy Degtyarev <va...@unipro.ru> wrote: >>> >>>> Hello, >>>> >>>> It seems that the 5080 port is closed. >>>> >>>> Please check. >>>> >>>> Thanks, >>>> Vasiliy >>>> >>>> >>>> On 17.07.2014 14:27, Huy Minh Huỳnh wrote: >>>> >>>> Hello everyone, >>>> >>>> I'm Huy from Vietnam (and quite a beginner to linux). >>>> Currently, I'm in charge of deploying a webinar/live conference >>>> server, then integrate it to moodle. >>>> I have selected OpenMeetings 3 and successfully installed on Debian 7 >>>> by following the guide "Quick Installation OpenMeetings 2.x on Wheezy". >>>> <https://cwiki.apache.org/confluence/download/attachments/27838216/Quick%20Installation%20OpenMeetings%202.x%20on%20Wheezy.pdf?version=1&modificationDate=1361176078000&api=v2> >>>> However after the installation, I have experienced weird situation >>>> relating to network accessing. >>>> I could access to OpenMeetings just fine if I use the web-browser of >>>> the server that contains OpenMeetings I just installed. (By open web >>>> browser on the server and surf http://localhost:5080/openmeetings/ or >>>> even http://192.168.100.100:5080/openmeetings whereas 192.168.100.100 >>>> is IP of the server I installed OpenMeetings). >>>> >>>> However, I could not use the outside clients to access it at all; I >>>> keep getting "Unable to connect" most of the time. Sometimes I successfully >>>> connect but a short moment afterward... I'm unable to connect again. >>>> >>>> Has anyone experienced this situation before? Or guiding me on how to >>>> analysis and fix this weird error? >>>> >>>> Thank in advance. >>>> >>>> Best regards, >>>> Huy. >>>> >>>> >>>> >>> >>> >>> -- >>> WBR >>> Maxim aka solomax >>> >> -- WBR Maxim aka solomax
