Jean-Marie,

 

If you solve the issue on how to use mod_proxy via your apache server, please 
let me know as I was never able to get this to work.

 

The solution that worked for me was to use two external IP addresses for our 
company. One for our web server and one for OpenMeetings, and then modify the 
listening ports 5080 and 8080 to both be port 80.  The OpenMeetings server does 
not have Apache or any other web server installed to it. 

 

Are you in a position to have more than one IP address for people in the 
internet to access both your Web server and you OpenMeetings server via port 60?

 

Thanks,

 

George Kirkham

 

 

 

From: Jean-Marie Landri [mailto:[email protected]] 
Sent: Thursday, 4 October 2012 12:14 AM
To: [email protected]
Subject: Re: error with moodle plugin

 

Sir,
Will you guide me to document about how to configure mod_proxy

Thank you

On Wed, Oct 3, 2012 at 5:42 AM, Maxim Solodovnik <[email protected]> wrote:

You have Apache already running on port 80.

you need to stop it before running red5 or configure mod_proxy

 

On Wed, Oct 3, 2012 at 9:33 AM, Jean-Marie Landri <[email protected]> 
wrote:

i just -
stopped red5 services 
configured the 2 files : $RED5_HOME/conf/red5.properties and 
$RED5_HOME/webapps/openmeetings/config.xml
restart red5
when loging to http://216.224.171.20:80/openmeetings/
redirecting to http://216.224.171.20/openmeetings/
and 404 error - " Not Found
The requested URL /openmeetings/ was not found on this server.
Apache/2.2.16 (Debian) Server at 216.224.171.20 Port 80

thank you

On Wed, Oct 3, 2012 at 4:17 AM, Maxim Solodovnik <[email protected]> wrote:

I mean "Configure alternative ports"

You need to change RTMPT port from 8088 (current) to 80

 

Or maybe event use apache+mod_proxy to redirect requests from 5080 to 80

 

On Wed, Oct 3, 2012 at 9:06 AM, Jean-Marie Landri <[email protected]> 
wrote:

Sir, did you mean this part;
Preventing Firewall issues 

________________________________

        A common way of bypassing the firewall is to change HTTP port to 80 and 
rtmpT to 443. 

        A short description about the connection mechanism: The application 
first tries connecting to rtmp 3 times, because rtmp is the protocol that is 
less performance hungry. If that fails the application will fallback to rtmpT. 

        Most firewalls do allow traffic on port 443 and they normally do not 
analyse the packets, because 443 is normally SSL encrypted, so the firewall 
should not be able to read the packets at all.????

 

On Wed, Oct 3, 2012 at 3:57 AM, Maxim Solodovnik <[email protected]> wrote:

I guess you have port issue then

try to set up RTMPT on port 80 (please see 
http://incubator.apache.org/openmeetings/PortSettings.html)

 

On Wed, Oct 3, 2012 at 8:51 AM, Jean-Marie Landri <[email protected]> 
wrote:

Sir,
in my moodle server i have no access to ssh shell

On Wed, Oct 3, 2012 at 3:45 AM, Maxim Solodovnik <[email protected]> wrote:

can you login to your moodle server and try "wget 
http://216.224.171.20:5080/openmeetings/services/UserService?wsdl";?

 

On Wed, Oct 3, 2012 at 8:43 AM, Jean-Marie Landri <[email protected]> 
wrote:

yes Sir

On Wed, Oct 3, 2012 at 3:40 AM, Maxim Solodovnik <[email protected]> wrote:

The URL works as expected now

Are you still expecting same moodle issue?

 

On Wed, Oct 3, 2012 at 12:26 AM, Jean-Marie Landri <[email protected]> 
wrote:

Please Sir,
You can check now..

Thank you

On Mon, Sep 24, 2012 at 4:08 AM, Maxim Solodovnik <[email protected]> wrote:

http://216.224.171.20:5080/openmeetings/services/UserService?wsdl

returns error 404 for me

same as http://216.224.171.20:5080/openmeetings/

 

I guess you have changed openmeetings in the URL to something else ....

You need to update URL in moodle plugin settings

 

On Mon, Sep 24, 2012 at 7:37 AM, Bakko <[email protected]> wrote:

The 5080 TCP Port on xxx.yyy.171.20 
<http://xxx.yyy.171.20:5080/openmeetings/services/UserService?wsdl>  is open?



El 23/09/2012 19:26, Jean-Marie Landri escribió:

        Someone Please?

        On Fri, Sep 14, 2012 at 6:32 AM, Jean-Marie Landri 
<[email protected]> wrote:

        Hello Sir
        We ping the IP from the server no problem:
        
        PING 216.224.171.20 (216.224.171.20) 56(84) bytes of data.
        64 bytes from 216.224.171.20: icmp_seq=1 ttl=55 time=28.7 ms
        64 bytes from 216.224.171.20: icmp_seq=2 ttl=55 time=28.7 ms
        64 bytes from 216.224.171.20: icmp_seq=3 ttl=55 time=28.7 ms
        64 bytes from 216.224.171.20: icmp_seq=4 ttl=55 time=28.8 ms
        64 bytes from 216.224.171.20: icmp_seq=5 ttl=55 time=28.7 ms
        64 bytes from 216.224.171.20: icmp_seq=6 ttl=55 time=28.7 ms
        ---------------

         

        On Sat, Sep 1, 2012 at 2:52 PM, [email protected] 
<[email protected]> wrote:

        You simply cannot connect from your moodle server to openmeetings.
        Try to login to your moodle server via SSH and do:
        "ping 216.224.171.20"
        And watch the output.
        
        Sebastian

        2012/8/29 Jean-Marie Landri <[email protected]>

        
        Hello
        i have installed moodle openmeetings plugin and set up openmeetings 
activity.
        i'm getting error :
        "
        Error
        
        wsdl error: Getting 
http://xxx.yyy.171.20:5080/openmeetings/services/UserService?wsdl - HTTP ERROR: 
cURL ERROR: 28: connect() timed out!
        url: http://216.224.171.20:5080/openmeetings/services/UserService?wsdl
        content_type: 
        http_code: 0
        header_size: 0
        request_size: 0
        filetime: -1
        ssl_verify_result: 0
        redirect_count: 0
        total_time: 30.001616
        namelookup_time: 0.000138
        connect_time: 0
        pretransfer_time: 0
        size_upload: 0
        size_download: 0
        speed_download: 0
        speed_upload: 0
        download_content_length: -1
        upload_content_length: -1
        starttransfer_time: 0
        redirect_time: 0
        certinfo: Array
        redirect_url: "
        I tried to uninstall and install it again but the same
        
        thank you

        
        
        
        -- 
        Sebastian Wagner
        https://twitter.com/#!/dead_lock <https://twitter.com/#%21/dead_lock> 
        http://www.webbase-design.de <http://www.webbase-design.de> 
        http://www.wagner-sebastian.com <http://www.wagner-sebastian.com> 
        [email protected] <mailto:[email protected]> 

         

         

 





 

-- 
WBR
Maxim aka solomax

 





 

-- 
WBR
Maxim aka solomax

 





 

-- 
WBR
Maxim aka solomax

 





 

-- 
WBR
Maxim aka solomax

 





 

-- 
WBR
Maxim aka solomax

 





 

-- 
WBR
Maxim aka solomax

 

Reply via email to