testing a red5 live streaming rtmp, plus creating a player for the rtmp

We created an app for live streaming here.

Now we going to test it and create a player code so we can start streaming to our site.

Do you have fmle installed on your computer? You need to download it from adobe.

Lets test it first, go to

http://209.95.39.220/test/

enter the rtmp of your app. the rtmp is

rtmp://server IP/app

so:

rtmp://RED5_SERVER_IP/live221

Enter this URL on the long string and click connect, now click “Publish” your camera will start,  and now click “Play” if the 2 players show the same thing you are on. Everything is good.

OK, now we have to work on “stream name”. We talked about rtmp, and we tested it, the testing site if you go back to it

http://209.95.39.220/test/

it has a stream name, “testing” this must be on both the publishing and on the player.

so it must be on the FMLE and on the player code.

fmle

(click on the image to have a better view)

the FMLE on the left you have your settings, frame per second, bitrate, your camera, format.

on the red5 server your bitrate should be about 320kbps higher then that you need a lot of RAM and server resources.

lets configure the fmle as the image shows.

on the right on the FMS URL enter the rtmp and on the stream enter your chosen stream name, in this case I entered “live” see image.

click connect, and then below click “Start”

you now streaming to your server.

 

Now creating a player for this stream. Go to

http://www.hosting-marketers.com/generator/

at the bottom on the “Streamer” enter the rtmp:

rtmp://RED5_SERVER_IP/live221

and on “Stream / File Name” enter the stream name, which we used on the FMLE, “live”

Click  “Generate Code!”

Take the “Preview & Embed” code, paste on your site and that’s it.

You can also use an image on the player, it will show before the user click to play,  enter the image URL on “Overlay Poster”

creating a new app on Red5 for live streaming

We will call this app live221.

first of all download the folder live from red5, the path is /usr/local/red5/webapps

if you ftp to the server you will see these apps.

then rename the folder live to live221

open the folder and go inside \WEB-INF folder, there are 3 files there, you need to change 2.

1- file: red5-web.properties
2 – file: web.xml

open on a text editor red5-web.properties , you will see the 2 lines below:
webapp.contextPath=/live
webapp.virtualHosts=*

change it to:

webapp.contextPath=/live221
webapp.virtualHosts=*

now open the second file web.xml the code on top:

red5 live app

upload the new folder, restart the Red5

go to the Red5 admin area and you will see the new app.

a few steps to protect your wordpress from hackers

1- Stay UPDATED – Run the latest version of WordPress, and upgrade your plugins and themes as quick as possible.
2- Have a strong password.
3- Disable PHP Execution in Certain WordPress Directories – This disables PHP execution in the upload directories and other directories of your choice. Basically so even if someone was able to upload the file in your uploads folder, they wouldn’t be able to execute it.
a- Block Access To wp-content Folder

The wp-content folder contains all your images, plugins and themes, it is a very important folder for your WordPress site. If this folder gets hacked they can delete all your themes and plugins on your site leaving your site blank.

To block access to your wp-content folder create a new htaccess file and save this at the root level of your wp-content folder.

Now add the following code in this new htaccess file.

Order deny,allow
Deny from all
<Files ~ “.(xml|css|jpe?g|png|gif|js)$”>
Allow from all
</Files>

b- Block file types being served from uploads and wp-includes

Having cleaned numerous WordPress hacks, in our experience most backdoor access files disguise themselves in /wp-includes/ folder or in your /wp-content/uploads/ directory. Usually these are .php files with names that some what seems like WordPress core files, but they are not. One of the measures that you can take to improve your WordPress security is disabling PHP execution in certain WordPress directories. We will show you how you can use .htaccess file to disable PHP execution in a specific directory.

Create a blank file in a text editor. Call it .htaccess and paste the following code in there:

<Files *.php>
deny from all
</Files>

Now upload this file in your /wp-content/uploads/ folder. You should also upload it in your /wp-includes/ folder.

Code Explanation: This code checks for any PHP file and denies access to it.

4- Delete themes and plugins you not using.
5- Deny access to the wp-config.php file.

Open your wordpress main .htaccess and paste the following code in there:

<Files wp-config.php>
Order Allow,Deny
Deny from all
</Files>

6= Disable Directory Browsing

If someone has access to your directories they will be able to view all the folders in this directory if you don’t have an index.html or a index.php file. You can stop this with htaccess by adding the following line the main .htaccess file, the one on the public_html. This will make sure that the hacker can not browse a directory even if an index file doesn’t exist.

# directory browsing
Options All -Indexes

7- Protect Against Requests That Haven’t Got A HTTP_USER_AGENT

You can stop this with htaccess by adding the below code to the main .htaccess file, the one on the public_html.

<IfModule mod_rewrite.c>
RewriteCond %{REQUEST_METHOD} POST
RewriteCond %{REQUEST_URI} .wp-comments-post\.php*
RewriteCond %{HTTP_REFERER} !.yourwebsite.com.* [OR]
RewriteCond %{HTTP_USER_AGENT} ^$
RewriteRule (.*) ^http://%{REMOTE_ADDR}/$ [R=301,L]
</IfModule>

Finally Good Luck!

Wowza Addons, Transcoder and Wowza nDVR added to our Wowza Packages

Hosting Marketers tries always to bring the latest and the best of web developments and at the best price. This time we proudly announce that we have introduced Wowza Transcoder and Wowza nDVR special Addons.

1- Wowza Transcoder

Transcoding is the process by which the digital file for a live video stream is ingested, decoded, and transformed into multiple file formats and bitrates to create different versions of the video for optimal viewing on various device types and at various bandwidths.

The transcoding feature of Wowza Streaming Engine is now available to our customers, what it does is transforms incoming live streams from encoders, IP cameras, IPTV headends, and other live sources to keyframe-aligned H.264 streams for adaptive bitrate delivery to any device, anywhere. This means the viewer will see the stream at the best possible bitrate possible to his internet connection, the better the internet connection the better the video quality, for viewers with low internet connection the video will be automatically adjusted to the best bitrate possible.

2- Wowza nDVR

Wowza nDVR, also available to our customers, allows live streaming to be recorded and the viewer to play or pause the live stream, rewind to a previously recorded point, or resume viewing at the current live point.

We also now allow our customers to record live streams directly to the wowza server with the option to start a new file every time the customer broadcasts, deleting previous file or append to the existing file.

Wowza packages can be ordered directly from https://hosting-marketers.com/wowza-hosting/

Node.js some information

As third-party software, Hosting Marketers does not support node.js beyond installation.
All our servers have node.js installed, but you need to configure it on your account, for that we need to know which port you using for the node, and you will need to create cron job and a bash file. The port we need to open it on our server firewall.

Create a file for example server.js on your account. on this file enter the code:

var http = require(“http”);
http.createServer(function(request, response) {
response.writeHead(200, {“Content-Type”: “text/plain”});
response.write(“Hello World”);
response.end();
}).listen(5002);

the number 5002 is your node port, open a ticket and explain that you going to use node and you want port 5002 opened.

Now in case this is your own vps or a dedicated server:
then create a file for example node.sh and on this file enter the below code:

#!/bin/bash
PGREP=”/usr/bin/pgrep”
NODE=”node”
$PGREP ${NODE}
if [ $? -ne 0 ]
then
/usr/local/bin/node /home/cpanel-username/public_html/server.js> /dev/null 2>&1
fi

we are assuming your first file is server.js.

Now create cron job for the node.sh, this file should be on 755 permissions.
the cron can be:

*/10 * * * * sh /home/cpanel-username/public_html/node.sh >/dev/null 2>&1

this will mean the server will check every 10 minutes if the node is working and restart if it goes down.

this can apply to any script which uses node.js

then to test if the system is working call on your browser:

http://domain:5002
the page should load:
Hello World

But if you are on a shared hosting:
You cannot use the node.sh option because when it pgrep it will find that there is other node process going on so it will not start yours. You will have to contact us so that we use the SCREEN option which will leave the process running on background even when we close the cmd window.
so we open cmd and type
screen
/usr/local/bin/node /home/cpanel-username/public_html/server.js
CTRL D + A
this will close the window and the process will continue, to test
http://domain:5002
the page should load:
Hello World

Important updates, news, reviews of our customers sites and tricks for common problems…