I made some changes in the /etc/hosts and now the following situation occurs.
The Moodle plugin is configured with the defaults and openmeetings_red5host to be localhost. Right now my /etc/hosts is: ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 127.0.0.1 localhost.localdomain localhost IP host.domain.net host The following request URL http://domain.net:5080/openmeetings/?secureHash=61901e1ddc64f8dd5a6c99aadc9400f6&scopeRoomId=10&language=1&user_id=2&moodleRoom=1&wwwroot=http://domain.net worked fine when i tried to access it from the browser and managed to create a room. When i tried to go into the same room from the Moodle website, inside the iframe that the room should be loaded i had instead a Error 102 (net::ERR_CONNECTION_REFUSED): The server refused the connection. At this point i am more about to think that it is a /etc/hosts file problem. Have you run into an issue like that before? On Mon, Jun 17, 2013 at 8:06 AM, Alexei Fedotov <[email protected]>wrote: > Hello Const, > That may not be the solution you seek. Please double check the plugin > configuration. > 17.06.2013 4:07 пользователь "Constantinos Ntzoufras" < > [email protected]> написал: > > FYI, the request >> http://host.domain.net:5080/openmeetings/?secureHash=8b44248aa73d1793ba670ad1d43a5e74&scopeRoomId=9&language=1&user_id=2&moodleRoom=1&wwwroot=http://host.domain.net >> worked >> fine when i tried to access it from the server, created a new room and >> logged me in to use it. >> It just does not seem to work with the Moodle plugin, or the requests >> that can be made. >> >> >> On Mon, Jun 17, 2013 at 3:04 AM, Constantinos Ntzoufras < >> [email protected]> wrote: >> >>> I managed to trace the request and noticed the following thing now. >>> When i was on the inspect element of Google Chrome and had the >>> OpenMeetings plugin configured with the Red5 host to be "localhost" in the >>> settings of the plugin onto the website i saw the following request >>> being made: >>> http://host.domain.net:5080/openmeetings/?secureHash=8b44248aa73d1793ba670ad1d43a5e74&scopeRoomId=9&language=1&user_id=2&moodleRoom=1&wwwroot=http://host.domain.net >>> and when i changed the Red5 host to be "http://host.domain.com"; i had >>> a "Request OpenMeetings! OpenMeetings Service failed and no response >>> was returned." error. >>> Is there any extra configuration that i should make on the OpenMeetings >>> server ? >>> Hope i gave some usefull info. >>> >>> Thanks alot, >>> >>> >>> >>> On Mon, Jun 17, 2013 at 2:40 AM, Constantinos Ntzoufras < >>> [email protected]> wrote: >>> >>>> In the ping i get the IP of the server. My Moodle installation is a >>>> 2.4+. I moved it to a new IP so i do not really think it is an issue that >>>> the ISP is blocking anything. I am still able to access my OpenMeetings >>>> server from http://host.domain.com:5080 and my Moodle site. But still >>>> when i load the frame of an OpenMeetings room in the Moodle website it >>>> gives me the >>>> Error 109 (net::ERR_ADDRESS_UNREACHABLE): Unable to reach the server. >>>> >>>> Could it be a Moodle problem with the version, possibly not being >>>> compatible with the OpenMeetings plugin I am using that one >>>> https://builds.apache.org/view/M-R/view/OpenMeetings/job/OpenMeetings%20Moodle%20Plugin/ >>>> ? >>>> >>>> The setup is pretty much clear, with just the OpenMeetings server and >>>> the Moodle website in localhost. >>>> debug.swf does not show any errors so i can suppose it's functioning >>>> but something else is happening. >>>> Is there any way i could trace the requests and find out to what IP or >>>> URL is the exact request so i can identify the problem? >>>> >>>> Thanks, >>>> >>>> >>>> On Fri, Jun 14, 2013 at 4:10 AM, George Kirkham <[email protected] >>>> > wrote: >>>> >>>>> Hi Constantinos,**** >>>>> >>>>> ** ** >>>>> >>>>> Are you able to access OpenMeetings without Moodle, that is access >>>>> OpenMeeting directly ? What happens both internally and externally (i.e. >>>>> via the Internet) when you access just OpenMeetings by itself?**** >>>>> >>>>> Using either**** >>>>> >>>>> http://host.domain.com:5080/openmeetings/**** >>>>> >>>>> or**** >>>>> >>>>> http:// xxx.xxx.xxx.xxx:5080/openmeetings/**** >>>>> >>>>> or both ?**** >>>>> >>>>> ** ** >>>>> >>>>> You said “my Moodle installation is configured with a public domain >>>>> name”, I do not know your set up, but I use an internal Debian DNS >>>>> server which manages internal (i.e. local LAN) connections to my web >>>>> server >>>>> and to OpenMeetings so that on my LAN I can access my web site just like >>>>> people who are external (i.e. who are accessing via the Internet). A very >>>>> similar solution is just to put an entry into your client computer’s host >>>>> file, doing this allows me to access my servers via their public domain >>>>> name, even if the IP address is not the same as the public IP address for >>>>> my domain.**** >>>>> >>>>> ** ** >>>>> >>>>> For example in my Windows client computer;**** >>>>> >>>>> *C:\Windows\System32\drivers\etc\hosts* >>>>> >>>>> # localhost name resolution is handled within DNS itself.**** >>>>> >>>>> # 127.0.0.1 localhost**** >>>>> >>>>> # ::1 localhost**** >>>>> >>>>> xxx.xxx.xxx.xxx host.domain.com**** >>>>> >>>>> ** ** >>>>> >>>>> Where xxx.xxx.xxx.xxx is the IP address of the OpenMeetings and/or >>>>> moodle server that I can ping using;**** >>>>> >>>>> C:\ping xxx.xxx.xxx.xxx**** >>>>> >>>>> ** ** >>>>> >>>>> And should return something like;**** >>>>> >>>>> ** ** >>>>> >>>>> Pinging host.domain.com [xxx.xxx.xxx.xxx] with 32 bytes of data:**** >>>>> >>>>> Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=63**** >>>>> >>>>> Reply from xxx.xxx.xxx.xxx: bytes=32 time<1ms TTL=63**** >>>>> >>>>> Reply from xxx.xxx.xxx.xxx: bytes=32 time=1ms TTL=63**** >>>>> >>>>> Reply from xxx.xxx.xxx.xxx: bytes=32 time=1ms TTL=63**** >>>>> >>>>> ** ** >>>>> >>>>> Ping statistics for xxx.xxx.xxx.xxx:**** >>>>> >>>>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),**** >>>>> >>>>> Approximate round trip times in milli-seconds:**** >>>>> >>>>> Minimum = 0ms, Maximum = 1ms, Average = 0ms**** >>>>> >>>>> ** ** >>>>> >>>>> If you have the entry correctly set in hosts file, then “C:\ping >>>>> host.domain.com” should return very similar results.**** >>>>> >>>>> ** ** >>>>> >>>>> I hope that some of the above ideas might be of help to you.**** >>>>> >>>>> ** ** >>>>> >>>>> Thanks,**** >>>>> >>>>> ** ** >>>>> >>>>> George Kirkham**** >>>>> >>>>> ** ** >>>>> >>>>> ** ** >>>>> >>>>> *From:* Constantinos Ntzoufras [mailto:[email protected]] >>>>> *Sent:* Friday, 14 June 2013 10:38 AM >>>>> *To:* [email protected] >>>>> *Subject:* RE: Error 109 (net::ERR_ADDRESS_UNREACHABLE): Unable to >>>>> reach the server.**** >>>>> >>>>> ** ** >>>>> >>>>> I have not tried to access an OpenMeetings room from inside Moodle in >>>>> my local LAN because my Moodle installation is configured with a public >>>>> domain name. At this time i cannot access an Openmeetings room from inside >>>>> Moodle, even though i am able to access my Openmeetings server and get in >>>>> the frame inside Moodle the error 109. >>>>> I hope i was clear as possible.**** >>>>> >>>>> On Jun 14, 2013 3:32 AM, "George Kirkham" <[email protected]> >>>>> wrote:**** >>>>> >>>>> Hi,**** >>>>> >>>>> **** >>>>> >>>>> Are you saying that Moodle and OpenMeetings are working correctly on >>>>> the local LAN, but when accessing externally from the Interent there are >>>>> connection problems ?**** >>>>> >>>>> **** >>>>> >>>>> You said;**** >>>>> >>>>> “Could it be an issue that the request to the openmeetings server is >>>>> coming from an address which looks like http://host.domain.com:port/and >>>>> not the usual >>>>> http://host.domain.com/ (in other words if there is a problem that >>>>> the request is coming from a url that has a port as well)”, I don’t >>>>> believe that the addition of the port number should be a problem. This has >>>>> never been a issue for myself. This just tells the web browser to use a >>>>> port other than port 80 when initiating the connection to the server.* >>>>> *** >>>>> >>>>> **** >>>>> >>>>> I can only suggest that there is something is either *blocking* or *not >>>>> forwarding* one of the default OpenMeetings ports 5080, 1935, 8088, >>>>> to your server ?**** >>>>> >>>>> **** >>>>> >>>>> What messages are you getting when you access >>>>> http://host.domain.com:5080/openmeetings/ ?**** >>>>> >>>>> **** >>>>> >>>>> Is there anything logs in the red5/log/ folder that indicates the >>>>> issue?**** >>>>> >>>>> **** >>>>> >>>>> http://openmeetings.apache.org/installation.html**** >>>>> >>>>> Use the Debug-Application: Enter in your browser >>>>> http://$RED-HOST:$RED5-PORT/openmeetings/?swf=maindebug.as3.swf11.swffor >>>>> example http://localhost:5080/openmeetings/?swf=maindebug.as3.swf11.swf >>>>> **** >>>>> >>>>> http:// host.domain.com:5080/openmeetings/?swf=maindebug.as3.swf11.swf >>>>> <http://localhost:5080/openmeetings/?swf=maindebug.as3.swf11.swf>**** >>>>> >>>>> **** >>>>> >>>>> **** >>>>> >>>>> http://openmeetings.apache.org/RTMPSAndHTTPS.html**** >>>>> >>>>> **** >>>>> >>>>> **** >>>>> >>>>> Thanks,**** >>>>> >>>>> **** >>>>> >>>>> George Kirkham**** >>>>> >>>>> **** >>>>> >>>>> **** >>>>> >>>>> **** >>>>> >>>>> *From:* Constantinos Ntzoufras [mailto:[email protected]] >>>>> *Sent:* Friday, 14 June 2013 7:46 AM >>>>> *To:* [email protected] >>>>> *Subject:* Error 109 (net::ERR_ADDRESS_UNREACHABLE): Unable to reach >>>>> the server.**** >>>>> >>>>> **** >>>>> >>>>> I have a problem that i have not managed yet to figure out.**** >>>>> >>>>> **** >>>>> >>>>> I have installed the OpenMeetings server and the OpenMeetings Moodle >>>>> plugin for a Moodle website that i run on the same machine. The machine's >>>>> operating system is CentOS 6.4.**** >>>>> >>>>> **** >>>>> >>>>> In my LAN i can access directly from every device/workstation the >>>>> Moodle website (which runs in port 7777 instead of 80) and the >>>>> Openmeetings >>>>> server (in port 5080)**** >>>>> >>>>> From a different network though, (e.g. from my work), even though i am >>>>> able to connect to the Moodle Website (on the same port as in my LAN 7777) >>>>> and the Openmeetings server (5080) i am not able to connect to a test >>>>> openmeetings room from the Moodle Plugin.**** >>>>> >>>>> **** >>>>> >>>>> The exact case is that i have created a test openmeetings room and >>>>> when i try to access it i get a **** >>>>> >>>>> **** >>>>> >>>>> Error 109 (net::ERR_ADDRESS_UNREACHABLE): Unable to reach the server.* >>>>> *** >>>>> >>>>> **** >>>>> >>>>> inside the OpenMeetings frame in the Moodle website, from Google >>>>> Chrome. **** >>>>> >>>>> **** >>>>> >>>>> I have added in my router every port (5080, 8088, 9999, 1935, 4445, >>>>> 8443) and on my CentOS machine i have added all of these ports on the >>>>> firewall, with SELinux disabled.**** >>>>> >>>>> **** >>>>> >>>>> A main problem is that my ISP is blocking requests to my public ip >>>>> from my LAN,**** >>>>> >>>>> in other words i cannot access my.exampleserver.network.net from >>>>> inside my LAN.**** >>>>> >>>>> Plus, i am not able to use ports 80 and 8080 to run the website there >>>>> because my ISP blocks them so as not to collide with the web interface of >>>>> the router that runs there.**** >>>>> >>>>> **** >>>>> >>>>> Could it be an issue that the request to the openmeetings server is >>>>> coming from an address which looks like http://host.domain.com:port/and >>>>> not the usual >>>>> http://host.domain.com/ (in other words if there is a problem that >>>>> the request is coming from a url that has a port as well)**** >>>>> >>>>> **** >>>>> >>>>> Thank you**** >>>>> >>>>> **** >>>>> >>>>> -- >>>>> Constantinos Ntzoufras **** >>>>> >>>> >>>> >>>> >>>> -- >>>> Constantinos Ntzoufras >>>> >>> >>> >>> >>> -- >>> Κωνσταντίνος Ντζούφρας >>> Constantinos Ntzoufras >>> >> >> >> >> -- >> Κωνσταντίνος Ντζούφρας >> Constantinos Ntzoufras >> > -- Κωνσταντίνος Ντζούφρας Constantinos Ntzoufras
