MT5 on Raspberry Pi not showing up.

[ghost]

Hi! I was looking a long time for something like MT5 and was about to start my own project creating a multitrack-player but MT5 was exactly what I was looking for!
I'm trying to use my Raspberry Pi as a webhost for MT5 but I can't make it work.
I have followed the instructions from github and have gotten everything installed and when I run "node server.js" I get "MT5 server listening at 127.0.0.1:8081".
On my laptop I'm now trying to access it by typing "192.168.1.8:8081" where 192.168.1.8 is my Raspberrys IP but there is nothing on that address. I have bin able to run other applications like Sickbeard on my Pi without problems so I don't know what the problem is.
My guess is that it's not sending out as a web-host and only works locally on my Pi but how can I make MT5 accessible from another computer like you have done on your test?

I really hope I can get MT5 up and running as I'm intending to create a improved UI made for smartphones and tablets so I can use it while practicing my instrument-playing.

Thank you for your help!
//Jacob Danell

[micbuffa]

Hmmm this is really strange... let me give a look at the server.js file...

Well, look at these lines, normally they should write to the server console
the ip and port the server is listening to...
If this seems ok, then it's certainly a problem with the firewall/proxy of
the pi... you can try to set up the addIP variable manually... but normally
it works as is.

// launch the http server on given port
server.listen(PORT || 3000, addrIP || "0.0.0.0", function(){
var addr = server.address();
console.log("MT5 server listening at", addr.address + ":" + addr.port);
});

Le sam. 2 juil. 2016 à 02:53, utjduo [email protected] a écrit :

Hi! I was looking a long time for something like MT5 and was about to
start my own project creating a multitrack-player but MT5 was exactly what
I was looking for!
I'm trying to use my Raspberry Pi as a webhost for MT5 but I can't make it
work.
I have followed the instructions from github and have gotten everything
installed and when I run "node server.js" I get "MT5 server listening at
127.0.0.1:8081".
On my laptop I'm now trying to access it by typing "192.168.1.8:8081"
where 192.168.1.8 is my Raspberrys IP but there is nothing on that address.
I have bin able to run other applications like Sickbeard on my Pi without
problems so I don't know what the problem is.
My guess is that it's not sending out as a web-host and only works locally
on my Pi but how can I make MT5 accessible from another computer like you
have done on your test?

I really hope I can get MT5 up and running as I'm intending to create a
improved UI made for smartphones and tablets so I can use it while
practicing my instrument-playing.

Thank you for your help!
//Jacob Danell

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12, or mute the thread
https://github.com/notifications/unsubscribe/AAnl2GJNZ2ZAX1QIvuNcq7QnsAA9h8nJks5qRbaCgaJpZM4JDkTs
.

[micbuffa]

Try to change the port to 80, if it's not already used. Sometimes
routers/nat filter non standard ports. Configure this on your router if you
want to stay with 8081. I really think that it's not a problem with the
server.js code

Le sam. 2 juil. 2016 à 08:43, michel buffa [email protected] a écrit :

Hmmm this is really strange... let me give a look at the server.js file...

Well, look at these lines, normally they should write to the server
console the ip and port the server is listening to...
If this seems ok, then it's certainly a problem with the firewall/proxy of
the pi... you can try to set up the addIP variable manually... but normally
it works as is.

// launch the http server on given port
server.listen(PORT || 3000, addrIP || "0.0.0.0", function(){
var addr = server.address();
console.log("MT5 server listening at", addr.address + ":" + addr.port);
});

Le sam. 2 juil. 2016 à 02:53, utjduo [email protected] a écrit :

Hi! I was looking a long time for something like MT5 and was about to
start my own project creating a multitrack-player but MT5 was exactly what
I was looking for!
I'm trying to use my Raspberry Pi as a webhost for MT5 but I can't make
it work.
I have followed the instructions from github and have gotten everything
installed and when I run "node server.js" I get "MT5 server listening at
127.0.0.1:8081".
On my laptop I'm now trying to access it by typing "192.168.1.8:8081"
where 192.168.1.8 is my Raspberrys IP but there is nothing on that address.
I have bin able to run other applications like Sickbeard on my Pi without
problems so I don't know what the problem is.
My guess is that it's not sending out as a web-host and only works
locally on my Pi but how can I make MT5 accessible from another computer
like you have done on your test?

I really hope I can get MT5 up and running as I'm intending to create a
improved UI made for smartphones and tablets so I can use it while
practicing my instrument-playing.

Thank you for your help!
//Jacob Danell

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#12, or mute the thread
https://github.com/notifications/unsubscribe/AAnl2GJNZ2ZAX1QIvuNcq7QnsAA9h8nJks5qRbaCgaJpZM4JDkTs
.

[ghost]

I tried changing the port to 80, no difference. Tride hardcode the IP and Port, no difference.
I installed nodejs on my windows computer, setup everything and run MT5. Localy it's working without any problems but I couldn't access it ether from any other device on my LAN.
Have you tried it yourself with the latest code on a clean install? Maybe it's something to do with socket.io?

[micbuffa]

There is no socket.io in mt5.

Hmmm I have a raspberry here, I will try this we. It should work, as the
demo version is just files copied on a remote server.

Le sam. 2 juil. 2016 à 12:11, utjduo [email protected] a écrit :

I tried changing the port to 80, no difference. Tride hardcode the IP and
Port, no difference.
I installed nodejs on my windows computer, setup everything and run MT5.
Localy it's working without any problems but I couldn't access it ether
from any other device on my LAN.
Maybe it's something to do with socket.io?

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#12 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AAnl2OceGv01zPA9UVKyRN4urZoe6oaHks5qRjlWgaJpZM4JDkTs
.

[ghost]

Ah ok. I saw in package.json that it said "socket.io": "~0.9.14" so I guessed it used socket.io.
Thanks!

[ghost]

Any luck on getting this working?