hi i'm running the red5 media server on my win 2003 server, it's assigned to its own IP-address. i've set up a testcase using jwplayer for streaming a video, unfortunately it doesn't work as expected (works locally, ports are open, when using port 5080 i can run the red5-demos from external)
i'm using the following settings for jwplayer:
jwplayer('mediaspace').setup({
'flashplayer': 'player.swf',
'file': 'test.flv',
'protocol': 'rtmp',
'streamer': 'rtmp://myserver.com:1935',
'controlbar': 'bottom',
'width': '470',
'height': '320'
});
the problem is that jwplayer shows up an error:
Server not found: rtmpt://myserver.com:80
although i've defined protocol rtmp on port 1935, jwplayer is trying to use rtmpt on port 80? any ideas what's wrong? thanks
I think JWPlayer tries by default to fallback to RTMPT on port 80.
So that message:
Server not found: rtmpt://myserver.com:80
could be translated in the humen readable message:
I tried to connect to rtmp://myserver.com:1935, was not able to connect,
falled back to rtmpT (rtmp over HTTP Tunneling to bypass firewalls)
on port 80. But still failed
Sebastian
Related
I have server on PORT 22, I connect to this server on PuTTY correctly by this port. But when I start the server using http-server command in PuTTY and type the IP in browser, I just get Index of/ showing folder structure.
In my simple app.js I have got
app.get("/", function(req,res){res.send("test")});
It doesn't work anyway. Does someone know what am I suposed to do?
I created my App from this boilerplate
https://github.com/Bikranshu/express-react-boilerplate
Now I uploaded it to a live Linux server and Node server is running.
Screenshot of running server
But I am unable to access it through Browser with IP address of server.
http://ip_address:3000
After waiting long in browser it is showing timeout error.
Please guide me how can I access the node/react app from browser.
Server running at <ipaddress> is a local IP, are you in a different network than the server? If so, you should be typing https://<public ipaddress>:3000
UPDATE
Hosting services usually only forward port 80 (http) or 443 (https.) This means that your port 3000 is not allowed for public access. To fix your problem you need to change the listening port.
Check line 42 on
server/app.js change 'port' to "80" or check package.json and edit npm start to set port to 80
So I've tried making my server listen on IP - 0.0.0.0 and on port 8080, then when I open up the browser (Chrome) and type https://192.168.0.1:8080/, Chrome says 'This site can’t be reached'. Although when I run the server in the CMD it starts working totally fine, which I think should be a sign for the server actually running somewhere.
Everyone's help is very appreciated!
Im running my node app with grunt on a DO droplet. I start the server
Running "connect:server" (connect) task
Waiting forever...
Started connect web server on http://localhost:3000
But when I navigate to my dropletIP:3000 I cannot see the app, I get:
This site can’t be reached
mydropletIP refused to connect.
Shouldn't my app be available? I don't have nginx or anything installed.
I was having similar problem but the solution was simple. Change from 'localhost' to '0.0.0.0' i.e
.listen(8080, '0.0.0.0');
And then to test your api just enter your static ip of droplet with port that you have entered i.e droplet-ip:8080
Check the particular port is opened or not ,using following command
sudo ufw status
If any Firewall enabled and any port is block means you can see that.
netstat -an | grep "LISTEN " ( List of listening port on server)
I need this info ,then only we can find a problem
I have installed Node.js with Socket.io on a CentOS server which is running Apache on port 80.
I created a socket test, which justs listens on port 8080.
If I curl the address localhost:8080 from within the server's shell, I get the Socket.io-welcome message. If I have a line like this:
<script src="http://localhost:8080/socket.io/socket.io.js"></script>
Then the browser cannot find the file.
A "solution" was to proxy requests to /nodejs/ to http://localhost:8080/, but this solution did not work for very long.
Is it possible to run the Node.js server when we have Apache installed? Which settings must be changed in order for us to access the url: http://server.com:8080 ? It seems the Node.js only accepts connections from localhost.
Problem is most probably in your node.js program.
It should listen on 0.0.0.0 and not 127.0.0.1 which is local only.
So where you've got something like:
.listen(8080, '127.0.0.1'); // '127.0.0.1' or 'localhost'
You should change it to:
.listen(8080); // or 0.0.0.0
Apache will only interfere if it also uses port 8080 but you should get an error when starting your node app if this is the case.
Also, if you connect to http://localhost in your browser, it will only work if the server is on the same local machine as the browser. Fine for testing I guess.
You'll have to connect to a domain or ip address if you have a hosted server else no browser will find it.
Update:
Your socket.io code also needs to connect correctly:
var socket = io.connect('http://correct.server.com:8080'); // not localhost
and your browser needs to load the javascript file from the correct place:
<script src="http://correct.server.com/socket.io/socket.io.js"></script> // not localhost
This might help with firewall / load balancer issues:
https://github.com/LearnBoost/socket.io/wiki/Socket.IO-and-firewall-software