I have load balancer that does ssl offloading and when i got prompted i said no to ssl why did it put port 443 ?
When offloading, it should indeed be 80 [HTTP].
Perhaps you passed along an answer file that has:
KALTURA_VIRTUAL_HOST_PORT="443"
from a prev. config attempt? or maybe you answered the SSL prompt with a Y by mistake?
Best re-run the config scripts and paste your answers here if there are still issues.
Regardless, curl -I -v https://portal.servcast.net needs to work, otherwise you’ll have issues making API requests.
In addition, all Kaltura Apache nodes have the X-Me header set:
/opt/kaltura/app/configurations/apache/conf.d/enabled.kaltura.conf
Header set X-Me "@KALTURA_VIRTUAL_HOST_NAME@"
but when I made the curl request to your LB [https://portal.servcast.net], I did not get this header, which makes me believe the actual Kaltura node is not even reached. Do you see the requests going through in the Apache access log? is the LB correctly routing to the Kaltura nodes?
Also, once the vhost configuration in /etc/httpd/conf.d/zzzkaltura.conf is fixed so that it listens on port 80 [which is what your LB expects] check whether you can reach the node directly and get the expected “start page”.
Indeed the problem was from my answer file… for some reason it had https and port 443 on it. Managed to install everything, i can access the plattform, everything seems alright.
OK, great.
Happy videoing,
Dear Jess,
I kinda got back to my original problem, VAST are now not working even in the studio, and even more some video do not play at all in the html studio player, but they do play in the flash player, also VAST does not work in the flash player as well.
Edit1: Seems i managed to resolve the VAST, they are working in the flash player now, but the html player won’t play some of my videos.
Hi @razvan_iacob,
# telnet nginx.servcast.net 88
fails for me. Does it work from the machine you’re trying to play from?
Yes, i had nginx.servcast.net… but afterwards we had to use the name somewhere else i just have it in the hosts file so that the servers do name resolutions.
this is the ip: 162.244.80.111
162.244.80.111 does answer on TCP 88 but if that’s the IP you want to use then you need to modify the DB records in kaltura.delivery_profile accordingly.
The player must be able to access Nginx to fetch the manifest and segments.
I’ll run the commands myself, i have the cluster on vlan, they work internally on internal ip.
telnet nginx.servcast.net 88
Trying 10.60.30.67…
Connected to nginx.servcast.net.
Escape character is ‘^]’.
Yes but are you able to connect to nginx.servcast.net on TCP port 88 from the machine where the player runs?
So the servers beween themsefls can access nginx.servcast.com, you can’t from the outside, as it has limited functionality on external ip.
Yes i can telnet from my computer to 162.244.80.111 88
I understand, so can I. But you need to be able to access nginx.servcast.com since that’s what the player is trying to connect to, on account of what you have set in kaltura.delivery_profile.
If you cannot, it will not work. You can change the delivery_profile records to use 162.244.80.111 instead.
Ok, but why do the videos work in the flash players and not in the html…, anyway, ca you please tell me how can i change the delivery profile to use 162.244.80.111 ?
Thanks.
The videos play with the Flash player because the Flash player [KDP] does not make use of the Nginx VOD module by default. It provides progressive HTTP playback, not HLS. The Flash player is legacy and we do not provide active support for it so I strongly recommend you avoid using it.
As for the delivery_profile table, simply update it so that all records that have nginx.servcast.com in the ‘url’ and host_name columns will have 162.244.80.111 instead.
So for instance:
url: http://nginx.servcast.com:88/dash
should become:
url: http://162.244.80.111:88/dash
Same for:
http://nginx.servcast.com:88/hls
http://nginx.servcast.com:88/hds
Eidt2 : mysql> select host_name from delivery_profile;
±--------------------+
| host_name |
±--------------------+
| portal.servcast.net |
| portal.servcast.net |
| NULL |
| NULL |
| NULL |
| NULL |
| NULL |
| NULL |
| NULL |
| nginx.servcast.net |
| nginx.servcast.net |
| nginx.servcast.net |
±--------------------+
12 rows in set (0.00 sec)
This doesn’t look right… shoulldn’t it have a single entry?
Here i should just have 162.244.80.111, correct ?
As I wrote, both host_name and url columns should be modified.
And yes, you will have multiple records, for partner 0 alone [which is used for all partners unless there is an entry that has their specific partner ID and matches the requested delivery profile] there are multiple entries. That’s because we provide HLS, HDS and DASH. By default, the HTML5 player uses HLS for playback but this can be changed. According to your screenshot, it seems you configured your player to use DASH. At any rate, since none of these will work with portal.servcast.net you should replace them all with the IP. Note that the url column includes more than just the hostname and you should be careful to only replace the hostname and not omit the ‘/dash’, ‘/hls’,’/hds’.