robertdoo / red5

Automatically exported from code.google.com/p/red5
0 stars 0 forks source link

RTMP stopped responding after changing IP #405

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hello Everyone,

I successfully build new version 1.0.1 with Java 1.7 and tried with JWPlayer. 
It was running fine but when I changed its IP for putting it in public for 
testing. It stopped working.

For Example: When I compiled and tested IP was 172.16.*.* and then I changed it 
to 202.164.*.* and it stopped working. When I put 172.16.*.* IP again it start 
responding.

Even when I am checking with netstat it is not listening on changed IP

OutPut with 172.16.*.* IP
tcp        0      0 ::ffff:172.16.*.*:1935       :::*                        
LISTEN      9906/java

OutPut with New IP
tcp        0      0 ::::1935       :::*                        LISTEN      
8256/java

in JWPlayer it is not listening on 127.0.0.1 IP so I had to change that IP 
also. Here is the JWPlayer code:

<script type="text/javascript">
    jwplayer("myElement").setup({
        file: "rtmp://172.16.*.*/oflaDemo/flv:startrekintodarkness_vp6.flv",
           height: 360,
           width: 640
           });
</script>

I also changed properties in red5.properties to 127.0.0.1 but working with 
172.16.*.* IP only.

# HTTP
http.host=127.0.0.1
http.port=5080
https.port=5443
http.URIEncoding=UTF-8
http.max_keep_alive_requests=-1
http.max_threads=20
http.acceptor_thread_count=10
http.processor_cache=20

# RTMP
rtmp.host=127.0.0.1
rtmp.port=1935
rtmp.io_threads=16
rtmp.send_buffer_size=65536
rtmp.receive_buffer_size=65536
rtmp.ping_interval=1000
rtmp.max_inactivity=60000
rtmp.max_handshake_time=5000
rtmp.tcp_nodelay=true
rtmp.default_server_bandwidth=10000000
rtmp.default_client_bandwidth=10000000
rtmp.client_bandwidth_limit_type=2
rtmp.bandwidth_detection=true
rtmp.encoder_base_tolerance=5000
rtmp.encoder_drop_live_future=false

Is it a know issue or something I am doing wrong. Please suggest.

Thanks,
Amit

Original issue reported on code.google.com by amit...@gmail.com on 11 Jun 2013 at 4:39

GoogleCodeExporter commented 9 years ago
If you're running on centos, replace 127.0.0.1 with localhost. I believe that's 
what I had to do on it or on osx; it's a bit foggy.

Original comment by mondain on 17 Jun 2013 at 7:41

GoogleCodeExporter commented 9 years ago

Original comment by mondain on 2 Jul 2013 at 6:36