Quantcast
Channel: Kaltura - Latest posts
Viewing all 7393 articles
Browse latest View live

Where to get authenticator code and what happen with flash player?

0
0

OK, awaiting your email.

Thanks,


Where to get authenticator code and what happen with flash player?

0
0

I just sent the email. If you don't see it then please check your spam folder.

Thanks

Where to get authenticator code and what happen with flash player?

0
0

did not get the email... didn't go to my spam dir either.. jess.portnoy@kaltura.com?

Where to get authenticator code and what happen with flash player?

0
0

Yes. that is the email I sent the information to from my admin at hiphopservers.com email. Did you check your SPAM folder or make sure my IP and domain are not blacklisted by your host. Alternately, you send me a email and I will reply to it with the information. You may need to add my address to your address book or white list.

Problems installing Kaltura CE on ubuntu 14.x

0
0

Hi,

I got a new error. I am not sure what is appropriate for these 2 values:

Apache port

KALTURA_VIRTUAL_HOST_PORT="443"
KALTURA_VIRTUAL_HOST_NAME="54.174.227.99"

My output is below.

root@ip-172-31-59-69:~# docker run -d --name=kaltura -p 80:80 -p 443:443 -p 1935:1935 kaltura/server
e361e9d8c26b0938c12cbdf9c94be4255529464afedf34161f82baf72a13885f
root@ip-172-31-59-69:~# nano
root@ip-172-31-59-69:~# docker cp config.ans kaltura:/root/install/
root@ip-172-31-59-69:~# docker exec -i -t kaltura /root/install/install.sh
setenforce: SELinux is disabled
Starting mysqld: [ OK ]
mysql-server-5.1.73-7.el6.x86_64
Stopping mysqld: [ OK ]
Starting mysqld: [ OK ]
Running base config...

kaltura-base-12.2.0-10.noarch
Welcome to Kaltura Server 12.2.0 post install setup.
Checking MySQL version..
Ver 5.1.73 found compatible

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_24_11_04_52.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================

Generating client libs...
This can take a few minutes to complete, see log at /opt/kaltura/log/generate.php.log.

    Configuration of 12.2.0 finished successfully!

Running FrontEnd config...

base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

kaltura-front-12.2.0-1.noarch

Enabling Apache config - apps.conf
Enabling Apache config - var.conf
Enabling Apache config - admin.conf

========================================================================================================================
Kaltura install answer file written to /tmp/kaltura_24_11_04_53.ans - Please save it!
This answers file can be used to silently-install re-install this machine or deploy other hosts in your cluster.
========================================================================================================================

Stopping httpd: [ OK ]
Starting httpd: httpd: Could not reliably determine the server's fully qualified domain name, using 172.17.0.2 for ServerName
[ OK ]
Stopping memcached: [ OK ]
Starting memcached: [ OK ]
Shutting down monit: [FAILED]
Starting monit: New Monit id: 836b0a02dba476dbe19342ed9441a5f0
Stored in '/root/.monit.id'
Starting Monit 5.18 daemon with http interface at [*]:2812
[ OK ]
sed: -e expression #1, char 41: unterminated s' command
sed: -e expression #1, char 21: unterminated
s' command

Running Sphinx config...

kaltura-sphinx-2.2.1-20.x86_64
base-config completed successfully, if you ever want to re-configure your system (e.g. change DB hostname) run the following script:

rm /opt/kaltura/app/base-config.lock

/opt/kaltura/bin/kaltura-base-config.sh

Starting monit: Starting Monit 5.18 daemon with http interface at [*]:2812
[ OK ]

Configuring your Kaltura DB...

Checking MySQL version..
Ver 5.1.73 found compatible

CREATE USER kaltura;
CREATE USER etl;
CREATE DATABASE kaltura;
CREATE DATABASE kaltura_sphinx_log;
CREATE DATABASE kalturadw;
CREATE DATABASE kalturadw_ds;
CREATE DATABASE kalturadw_bisources;
CREATE DATABASE kalturalog;
Checking connectivity to needed daemons...
Connectivity test passed:)
ERROR: Couldn't make an API request to https://54.174.227.99:443/api_v3/index.php?service=system&action=ping.
Please check your setup and then run /opt/kaltura/bin/kaltura-db-config.sh again.

Do you wish to remove the Kaltura DBs? [n/Y]
Hit 'n' to keep it for debugging purposes.

n
ERROR: we failed on something else..

Authenticator code on admin console + An error occurred

0
0

Hello,
This parameter does not exists in this file

KMC not found : /index.phpmodule=kmc/amp;action=kmc2

0
0

Actually it is not working, this morning the link

<a href="/index.php/kmc/kmc#dashboard|" target="_blank">Kaltura Management Console (KMC)</a>

is redirecting me to

http://streaming.xxxxxxxxfr/index.phpmodule=kmc/amp;action=kmc2#dashboard|

That's really strange, it is like when I used the admin console to force a login following by a logout then the login page is accessible... or it is link to my other problem to access to the admin console

Please help about intergation with wowza

0
0

Hi,

I have installed kaltura ce 12 recently. i was looking for doing livestreaming with it. i have created a live stream entry in KMC, but on providing rtmp url in adobe flash live media encoder it says incorrect url . i am using below url to connect .
rtmp://$NGINX_HOST:1935/kLive/stream


Using same ks with different client objects

0
0

Hello,

I am coding in javascript on the client side.
I would like to know if we can use the same KS with different KalturaClient objects ?
Because when I call the api media.listAction() a first time, I get correctly the list of medias, however when I refresh the page and call media.listAction() a second time by using a new KalturaClient object, but using the same ks than the first time (I have saved the ks in the browser session storage), I get as a result a KS string.
I don't understand why ?

Should I use always the same KalturaClient object with a specific KS string ? Then should I save the KalturaClient object in session storage as well.

Thank you in advance for your help !

Compiling the kaltura nginx with live rtmp

0
0

Name : kaltura-nginx
Arch : x86_64
Version : 1.10.2
Release : 3
Size : 1.8 M
Repo : installed
From repo : Kaltura
Summary : High performance web server customized for Kaltura VOD
URL : http://nginx.org/
License : 2-clause BSD-like license
Description : nginx [engine x] is an HTTP and reverse proxy server, as well as
: a mail proxy server.
: This is a custom Nginx build for the Kaltura VOD module.
: Please see: https://github.com/kaltura/nginx-vod-module for more info.

Server-side ad insertion

Compiling the kaltura nginx with live rtmp

0
0

OK, that's good. This version includes support for RTMP.
Are you having any issues when trying to stream?

Compiling the kaltura nginx with live rtmp

0
0

I am able to stream, the encoder is connects, I can see in /tmp/var/hlsme/ tmp/var/dashme stream chunks, but i cannot see the stream in any jwplayer or the kaltura player.

Using same ks with different client objects

0
0

Hello,

The Kaltura API is stateless and you should always pass the KS when making API requests that require authentication/authorization.

To generate a KS with the JS client, you need to call:

client.session.start(function(success, ks) {
...
},
secret,
userId,
type,
partnerId,
expiry,
privileges);
}

The ks var will then contain a string which is the KS [Kaltura Session] which you need to assign to the client using:

client.setKs(ks);

From there onwards, you can use this client with this KS to make subsequent calls, until that KS expires.

That said, you can use the same KS with different clients rather than generating a new one using session.start(). Of course, bear in mind a KS has an expiry field, when null is passed for the expiry param, expiry will be set to 86400 seconds, which is 24 hours.

My guess, without looking at your code, is that you forgot to call client.setKs(ks) for the second client, but it's just a guess.

There is a step by step code tutorial about generating a KS and assigning it here:
https://developer.kaltura.com/recipes/authentication#/start

and you can toggle code in several languages, including JS.

Additional code samples are available here:
https://developer.kaltura.com/recipes

If you still have issues with your code, please post an actual code snippet so I can help you further.

Compiling the kaltura nginx with live rtmp

0
0

I see. Please provide a sample embed page so I can take a look..
Thanks,


Please help about intergation with wowza

0
0

Hello,

I'm a little confused.. you wrote "wowza" in the subject but in your post you are referring to Nginx.
Which one is it?

Start by running:
# netstat -plnt |grep 1935

I assume you DO mean Nginx, which is provided by the kaltura-nginx package, which is fetched as a dependency when installing the kaltura-server package.

After making sure nginx is running and has a listener on port 1935 TCP, check if you can telnet to it from the machine you're trying to stream to, this can be done with:
# telnet $NGINX_HOST 1935

we can take it from there, based on the current situation.

Authenticator code on admin console + An error occurred

0
0

Hi @fravetier,

That will certainly account for the issue but I'm wondering how that can be..
Does it exist in /opt/kaltura/app/configurations/admin.template.ini?

This file comes from https://github.com/kaltura/server/blob/Lynx-12.6.0/configurations/admin.template.ini#L16
When running the post install script, the placeholders in this file are replaced with actual inputs and /opt/kaltura/app/configurations/admin.ini is created.

Anyhow, adding settings.remoteAddrHeaderSalt, setting it to the same value as remote_addr_header_salt in /opt/kaltura/app/configurations/local.ini and reload Apache should fix the issue.

Please let me know,

Compiling the kaltura nginx with live rtmp

Authenticator code on admin console + An error occurred

0
0

Hi,

the template exists, it contains :

settings.remoteAddrHeaderSalt = @APP_REMOTE_ADDR_HEADER_SALT@

I added settings.remoteAddrHeaderSalt following by the right value into /opt/kaltura/app/configurations/local.ini. I reloaded apache.
Now the form still contains the authenticator code but I do not need to fill it and I am able to access to the admin console.

This issue is closed.

Thank you very much!

Problems installing Kaltura CE on ubuntu 14.x

Viewing all 7393 articles
Browse latest View live




Latest Images