New Install, running but not accessing through the 4242

[Mohammad Rashidi]

hi everybody,

i've just upload libmist & mistserver and try to install by using "make && sudo make install"

now, as i entered MistController, this is displayed but i cant access to the whole server! it seems to block me!

let me know what is the next step?

system is running, but is out of order for me! and nothing is displayed by 4242!

[root@felan~]# MistController -n -i 5.61.24.73 -p 4242

No streams configured, remember to set up streams through the web interface on port 4242 or API.

(Nov 08 2014 -- 00:30) [CONF] Controller started

(Nov 08 2014 -- 00:30) [INFO] MistController|1311|lib/socket.cpp:704|IPv6 socket success @ 5.61.24.73:4242

(Nov 08 2014 -- 00:30) [INFO] MistController|1311|lib/config.cpp:392|Activating threaded server: MistController

(Nov 08 2014 -- 00:30) [CONF] Starting connector: {"connector":"HTTP"}

(Nov 08 2014 -- 00:30) [CONF] Starting connector: {"connector":"RTMP"}

(Nov 08 2014 -- 00:30) [INFO] MistOutRTMP|1329|lib/socket.cpp:704|IPv6 socket success @ 0.0.0.0:1935

(Nov 08 2014 -- 00:30) [INFO] MistOutRTMP|1329|lib/config.cpp:409|Activating forked server: /usr/bin/MistOutRTMP

(Nov 08 2014 -- 00:30) [INFO] MistConnHTTP|1328|lib/socket.cpp:704|IPv6 socket success @ 0.0.0.0:8080

(Nov 08 2014 -- 00:30) [INFO] MistConnHTTP|1328|lib/config.cpp:392|Activating threaded server: /usr/bin/MistConnHTTP

[Jaron Vietor]

Hello Mohammad,

You're binding the API port (4242) to the address 5.61.24.73 - this means you can only reach it at http://5.61.24.73:4242 (and not at localhost:4242, for example)

Of course, the machine running the server must actually be accessible at that address as well.

If you're not sure about the network configuration of the machine, simply leave out the -i option and the port will be open on all interfaces.

Hope that helped,

Regards,

Jaron Viëtor

CTO, DDVTech

 

[Mohammad Rashidi]

Hi Jaron, Thanks for your reply

i just start with MistController and server started.

but now, every request to the server to port 8080 or 4242 will be blocked! server just is working while i stop iptables!

this is the log:

Nov 8 11:20:42 mediaiksna kernel: [1066748.200133] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=109.203.190.3 DST=5.61.24.73 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=32225 DF PROTO=TCP SPT=54418 DPT=4242 WINDOW=8192 RES=0x00 SYN URGP=0

:(

[Mohammad Rashidi]

Hi Jaron, Thanks for your reply

i just start with MistController and server started.

but now, every request to the server to port 8080 or 4242 will be blocked! server just is working while i stop iptables!

this is the log:

Nov 8 11:20:42 mediaiksna kernel: [1066748.200133] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=109.203.190.3 DST=5.61.24.73 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=32225 DF PROTO=TCP SPT=54418 DPT=4242 WINDOW=8192 RES=0x00 SYN URGP=0

:(

[Mohammad Rashidi]

i also receive this on the terminal window:

(Nov 08 2014 -- 12:16) [INFO] MistInFLV|8377|lib/json.cpp:739|Ignored attempt to netpack a non-object.

does it related to the iptable and port blocking by it?

On Saturday, November 8, 2014 1:07:30 AM UTC+3:30, Mohammad Rashidi wrote:

[Mohammad Rashidi]

and also receiving this:

(Nov 08 2014 -- 13:08) [WARN] MistController|10014|lib/shared_memory.cpp:723|Client 0 timed out

[Jaron Vietor]

On Sat, Nov 8, 2014 at 9:34 AM, Mohammad Rashidi <iacti...@gmail.com> wrote:

Hi Jaron, Thanks for your reply

i just start with MistController and server started.

but now, every request to the server to port 8080 or 4242 will be blocked! server just is working while i stop iptables!

this is the log:

Nov 8 11:20:42 mediaiksna kernel: [1066748.200133] Firewall: *TCP_IN Blocked* IN=venet0 OUT= MAC= SRC=109.203.190.3 DST=5.61.24.73 LEN=48 TOS=0x00 PREC=0x00 TTL=113 ID=32225 DF PROTO=TCP SPT=54418 DPT=4242 WINDOW=8192 RES=0x00 SYN URGP=0

:(

Hello Mohammad,

We can't help you fix your iptables config, sorry.

For more information about working with iptables, look here:

http://wiki.centos.org/HowTos/Network/IPTables

Hope that helps,

Regards,

Jaron

PS: The two errors you're receiving in the terminal can be ignored - they are for debugging purposes only.